Network behavior of slow Windows shared storageUseful Command-line Commands on WindowsWindows Server 2008 R2 Shared folders are very slow when uploading filesVery poor network performance between Windows 7 and Server 2008 R2CPU is very spikey and erratic, network latency. Windows Server 2003Duplicating a file on a Windows fileshareWhen an Excel file is locked on a network share, how does it know who locked the file?IIS: How to tell if a slow time-taken is due to a slow network connectionWindows 7 extremely slow with samba 4Word 2013 is slow when opening files from network shareLarge-ish shared file directory very slow to open files
Does a centaur PC also count as being mounted?
Why does this function call behave sensibly after calling it through a typecasted function pointer?
The Puzzling Reverse and Add Sequence
Why won't the ground take my seed?
Was "I have the farts, again" broadcast from the Moon to the whole world?
What could a reptilian race tell by candling their eggs?
Analog is Obtuse!
How to convert object fill in to fine lines?
Averting Real Women Don’t Wear Dresses
Building a frequency dictionary from a Pandas dataframe
Does anycast addressing add additional latency in any way?
Can a single server be associated with multiple domains?
What's the safest way to inform a new user of their password on my web site?
In the context of a differentiator circuit, what is a “current-sensing resistor”?
How to determine what is the correct level of detail when modelling?
Can a US President have someone sent to prison?
Fluently Validation of Objects
Zombie diet, why humans?
One folder two different locations on ubuntu 18.04
Symbol for "not absolutely continuous" in Latex
How do accents of a whole town drift?
Which centaur is more 'official'?
How to start learning the piano again
Is there a short way to check uniqueness of values without using 'if' and multiple 'and's?
Network behavior of slow Windows shared storage
Useful Command-line Commands on WindowsWindows Server 2008 R2 Shared folders are very slow when uploading filesVery poor network performance between Windows 7 and Server 2008 R2CPU is very spikey and erratic, network latency. Windows Server 2003Duplicating a file on a Windows fileshareWhen an Excel file is locked on a network share, how does it know who locked the file?IIS: How to tell if a slow time-taken is due to a slow network connectionWindows 7 extremely slow with samba 4Word 2013 is slow when opening files from network shareLarge-ish shared file directory very slow to open files
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I have got on my hands 3 Windows XP file servers (their sole purpose is their SMB share) running on a office with about 50 users. The workload is only office usage: they use it to store and share among them Access databases and XLS files, and they use the files over the network share.
It is almost instantaneous to copy a 700 Kb XLS file from one of the servers to a workstation, but it takes over a minute to load it from a remote share with Excel. This same file is loaded in a few seconds if from a local disk.
I don't know what makes the access to the file so slow when using it via the network, I suspect it is some quirk of Windows remote file access (maybe authentication?), and I hope to be possible to change some simple flag on the servers to speed things up to a sane speed. I have taken screen shots of the network usage while loading the aforementioned XLS file, can you recognize this pattern and possibly give me some clue of what is the problem?
In the first image, there are two runs of Excel loading the remote file, both taking more than one minute to complete. The top and bottom graphs are from the same thing, but I only found later the task manager option to discriminate between upload (red) and download (yellow), so I took 2 different screenshots (concatenated bellow). Both runs took more than one minute, possibly more than 2 minutes.
In the second image there are the 3rd and 4th runs. This time they ran considerably faster than the first one, but still too slow for bearable use. Both took more than 1 minute, but in the 4th run it occurred to me to measure the time properly, and I found it to take 1 minute and 42 seconds. That was the fastest of them. This time I only took one screenshot, of the discriminated version.
What I noticed in all runs is the initial peak, about 8 seconds after I start the run, then the network usage drops to very low usage, then, a few seconds later, there is another peak, the biggest concentrated activity, then a long time of almost no activity, when finally Excel shows the file. There is still another peak that begins when the file is shown, and lasts for a few seconds. The offset between the start and end of the run, and the activity in the graph seems to be caused by a delay in the task manager to show the data. I don't know when the file is actually downloaded. I can't also explain why the green graph shows a small activity between peaks, and the red/yellow graph shows none. But the most intriguing of all is the minute long pause between the second and third peak, when I have no idea on what is happening, and certainly could be much faster.
Can someone experienced in Windows networks provide some expert guess on what is the problem with this setup (apart from decade old operating system)? Do you recognize these graph patterns? Can explain it? Have any hint on how to improve performance?
windows performance network-share server-message-block workgroup
edited Sep 25 '12 at 23:08
Skyhawk
13.5k3 gold badges45 silver badges91 bronze badges
asked Sep 4 '12 at 22:23
lvellalvella
2001 silver badge10 bronze badges
add a comment |
I have got on my hands 3 Windows XP file servers (their sole purpose is their SMB share) running on a office with about 50 users. The workload is only office usage: they use it to store and share among them Access databases and XLS files, and they use the files over the network share.
It is almost instantaneous to copy a 700 Kb XLS file from one of the servers to a workstation, but it takes over a minute to load it from a remote share with Excel. This same file is loaded in a few seconds if from a local disk.
I don't know what makes the access to the file so slow when using it via the network, I suspect it is some quirk of Windows remote file access (maybe authentication?), and I hope to be possible to change some simple flag on the servers to speed things up to a sane speed. I have taken screen shots of the network usage while loading the aforementioned XLS file, can you recognize this pattern and possibly give me some clue of what is the problem?
In the first image, there are two runs of Excel loading the remote file, both taking more than one minute to complete. The top and bottom graphs are from the same thing, but I only found later the task manager option to discriminate between upload (red) and download (yellow), so I took 2 different screenshots (concatenated bellow). Both runs took more than one minute, possibly more than 2 minutes.
In the second image there are the 3rd and 4th runs. This time they ran considerably faster than the first one, but still too slow for bearable use. Both took more than 1 minute, but in the 4th run it occurred to me to measure the time properly, and I found it to take 1 minute and 42 seconds. That was the fastest of them. This time I only took one screenshot, of the discriminated version.
What I noticed in all runs is the initial peak, about 8 seconds after I start the run, then the network usage drops to very low usage, then, a few seconds later, there is another peak, the biggest concentrated activity, then a long time of almost no activity, when finally Excel shows the file. There is still another peak that begins when the file is shown, and lasts for a few seconds. The offset between the start and end of the run, and the activity in the graph seems to be caused by a delay in the task manager to show the data. I don't know when the file is actually downloaded. I can't also explain why the green graph shows a small activity between peaks, and the red/yellow graph shows none. But the most intriguing of all is the minute long pause between the second and third peak, when I have no idea on what is happening, and certainly could be much faster.
Can someone experienced in Windows networks provide some expert guess on what is the problem with this setup (apart from decade old operating system)? Do you recognize these graph patterns? Can explain it? Have any hint on how to improve performance?
windows performance network-share server-message-block workgroup
edited Sep 25 '12 at 23:08
Skyhawk
13.5k3 gold badges45 silver badges91 bronze badges
asked Sep 4 '12 at 22:23
lvellalvella
2001 silver badge10 bronze badges
1
You should take a trace with Wireshark to be able to see what is actually being waited for. I would suspect locking issues.
– the-wabbit
Sep 4 '12 at 23:10
add a comment |
I have got on my hands 3 Windows XP file servers (their sole purpose is their SMB share) running on a office with about 50 users. The workload is only office usage: they use it to store and share among them Access databases and XLS files, and they use the files over the network share.
It is almost instantaneous to copy a 700 Kb XLS file from one of the servers to a workstation, but it takes over a minute to load it from a remote share with Excel. This same file is loaded in a few seconds if from a local disk.
I don't know what makes the access to the file so slow when using it via the network, I suspect it is some quirk of Windows remote file access (maybe authentication?), and I hope to be possible to change some simple flag on the servers to speed things up to a sane speed. I have taken screen shots of the network usage while loading the aforementioned XLS file, can you recognize this pattern and possibly give me some clue of what is the problem?
In the first image, there are two runs of Excel loading the remote file, both taking more than one minute to complete. The top and bottom graphs are from the same thing, but I only found later the task manager option to discriminate between upload (red) and download (yellow), so I took 2 different screenshots (concatenated bellow). Both runs took more than one minute, possibly more than 2 minutes.
In the second image there are the 3rd and 4th runs. This time they ran considerably faster than the first one, but still too slow for bearable use. Both took more than 1 minute, but in the 4th run it occurred to me to measure the time properly, and I found it to take 1 minute and 42 seconds. That was the fastest of them. This time I only took one screenshot, of the discriminated version.
What I noticed in all runs is the initial peak, about 8 seconds after I start the run, then the network usage drops to very low usage, then, a few seconds later, there is another peak, the biggest concentrated activity, then a long time of almost no activity, when finally Excel shows the file. There is still another peak that begins when the file is shown, and lasts for a few seconds. The offset between the start and end of the run, and the activity in the graph seems to be caused by a delay in the task manager to show the data. I don't know when the file is actually downloaded. I can't also explain why the green graph shows a small activity between peaks, and the red/yellow graph shows none. But the most intriguing of all is the minute long pause between the second and third peak, when I have no idea on what is happening, and certainly could be much faster.
Can someone experienced in Windows networks provide some expert guess on what is the problem with this setup (apart from decade old operating system)? Do you recognize these graph patterns? Can explain it? Have any hint on how to improve performance?
windows performance network-share server-message-block workgroup
edited Sep 25 '12 at 23:08
Skyhawk
13.5k3 gold badges45 silver badges91 bronze badges
asked Sep 4 '12 at 22:23
lvellalvella
2001 silver badge10 bronze badges
I have got on my hands 3 Windows XP file servers (their sole purpose is their SMB share) running on a office with about 50 users. The workload is only office usage: they use it to store and share among them Access databases and XLS files, and they use the files over the network share.
It is almost instantaneous to copy a 700 Kb XLS file from one of the servers to a workstation, but it takes over a minute to load it from a remote share with Excel. This same file is loaded in a few seconds if from a local disk.
I don't know what makes the access to the file so slow when using it via the network, I suspect it is some quirk of Windows remote file access (maybe authentication?), and I hope to be possible to change some simple flag on the servers to speed things up to a sane speed. I have taken screen shots of the network usage while loading the aforementioned XLS file, can you recognize this pattern and possibly give me some clue of what is the problem?
In the first image, there are two runs of Excel loading the remote file, both taking more than one minute to complete. The top and bottom graphs are from the same thing, but I only found later the task manager option to discriminate between upload (red) and download (yellow), so I took 2 different screenshots (concatenated bellow). Both runs took more than one minute, possibly more than 2 minutes.
In the second image there are the 3rd and 4th runs. This time they ran considerably faster than the first one, but still too slow for bearable use. Both took more than 1 minute, but in the 4th run it occurred to me to measure the time properly, and I found it to take 1 minute and 42 seconds. That was the fastest of them. This time I only took one screenshot, of the discriminated version.
What I noticed in all runs is the initial peak, about 8 seconds after I start the run, then the network usage drops to very low usage, then, a few seconds later, there is another peak, the biggest concentrated activity, then a long time of almost no activity, when finally Excel shows the file. There is still another peak that begins when the file is shown, and lasts for a few seconds. The offset between the start and end of the run, and the activity in the graph seems to be caused by a delay in the task manager to show the data. I don't know when the file is actually downloaded. I can't also explain why the green graph shows a small activity between peaks, and the red/yellow graph shows none. But the most intriguing of all is the minute long pause between the second and third peak, when I have no idea on what is happening, and certainly could be much faster.
Can someone experienced in Windows networks provide some expert guess on what is the problem with this setup (apart from decade old operating system)? Do you recognize these graph patterns? Can explain it? Have any hint on how to improve performance?
windows performance network-share server-message-block workgroup
windows performance network-share server-message-block workgroup
edited Sep 25 '12 at 23:08
Skyhawk
13.5k3 gold badges45 silver badges91 bronze badges
asked Sep 4 '12 at 22:23
lvellalvella
2001 silver badge10 bronze badges
edited Sep 25 '12 at 23:08
Skyhawk
13.5k3 gold badges45 silver badges91 bronze badges
asked Sep 4 '12 at 22:23
lvellalvella
2001 silver badge10 bronze badges
edited Sep 25 '12 at 23:08
Skyhawk
13.5k3 gold badges45 silver badges91 bronze badges
edited Sep 25 '12 at 23:08
Skyhawk
13.5k3 gold badges45 silver badges91 bronze badges
edited Sep 25 '12 at 23:08
Skyhawk
13.5k3 gold badges45 silver badges91 bronze badges
13.5k3 gold badges45 silver badges91 bronze badges
asked Sep 4 '12 at 22:23
lvellalvella
2001 silver badge10 bronze badges
asked Sep 4 '12 at 22:23
lvellalvella
2001 silver badge10 bronze badges
asked Sep 4 '12 at 22:23
lvellalvella
2001 silver badge10 bronze badges
2001 silver badge10 bronze badges
1
You should take a trace with Wireshark to be able to see what is actually being waited for. I would suspect locking issues.
– the-wabbit
Sep 4 '12 at 23:10
add a comment |
1
You should take a trace with Wireshark to be able to see what is actually being waited for. I would suspect locking issues.
– the-wabbit
Sep 4 '12 at 23:10
1
1
You should take a trace with Wireshark to be able to see what is actually being waited for. I would suspect locking issues.
– the-wabbit
Sep 4 '12 at 23:10
You should take a trace with Wireshark to be able to see what is actually being waited for. I would suspect locking issues.
– the-wabbit
Sep 4 '12 at 23:10
add a comment |
1 Answer
1
active
oldest
votes
If the "slowness" only happens in Excel, I would probably look closer at the XML file and make sure the interpreter in Excel isn't having trouble parsing the XML. Could be malformed or having some trouble reading it. Try opening the file in other applications like Notepad etc and see if the slowness issue still exists. FWIW, XP isn't a good platform for sharing files with that many (50) users as it is limited to 10 client connections. You could be running into some contention issues with the other clients trying to read the XML file as well. I don't think your issue is the size of the file, but rather what excel is doing with the file once it opens it. But that is just my thought. Try doing a CSV file dump and opening it up in Excel and see how long that takes.
answered Sep 4 '12 at 22:43
MikeAWoodMikeAWood
2,3811 gold badge8 silver badges13 bronze badges
First, I had it wrong, it is not XML, it is XLS... an ordinary XLS. Secondly, the file opens OK when local.
– lvella
Sep 4 '12 at 22:51
a 700K excel doc should be fine. a few more things to check. In computer management, under shared folders, check under sessions and open files. Looks to see how many users are attached in there. XLS really doesn't like to "share" files and have multiple copies opened remotely. It could just be simple file contention. If you put another copy somewhere else on the share that non of the other users are using, does the problem still exist?
– MikeAWood
Sep 4 '12 at 22:56
I'll check it... but the chances of file contention on that particular file I used for testing are extremely remote, since it was choose randomly from one of too many archived old processes.
– lvella
Sep 5 '12 at 0:31
contention might be related to the 10 client connection limits. Certainly worth a look. Is this a new issue or something that has always happened?
– MikeAWood
Sep 5 '12 at 0:55
People there said the problem was related to the new VoIP phone installed on every table, bridging the central switch and the workstation (supposedly interfering with the network), but tests made with and without the phone made no significant difference. If are there any other factors that caused the issue, I don't know.
– lvella
Sep 5 '12 at 1:05
|
show 1 more comment
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f424341%2fnetwork-behavior-of-slow-windows-shared-storage%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
If the "slowness" only happens in Excel, I would probably look closer at the XML file and make sure the interpreter in Excel isn't having trouble parsing the XML. Could be malformed or having some trouble reading it. Try opening the file in other applications like Notepad etc and see if the slowness issue still exists. FWIW, XP isn't a good platform for sharing files with that many (50) users as it is limited to 10 client connections. You could be running into some contention issues with the other clients trying to read the XML file as well. I don't think your issue is the size of the file, but rather what excel is doing with the file once it opens it. But that is just my thought. Try doing a CSV file dump and opening it up in Excel and see how long that takes.
answered Sep 4 '12 at 22:43
MikeAWoodMikeAWood
2,3811 gold badge8 silver badges13 bronze badges
First, I had it wrong, it is not XML, it is XLS... an ordinary XLS. Secondly, the file opens OK when local.
– lvella
Sep 4 '12 at 22:51
a 700K excel doc should be fine. a few more things to check. In computer management, under shared folders, check under sessions and open files. Looks to see how many users are attached in there. XLS really doesn't like to "share" files and have multiple copies opened remotely. It could just be simple file contention. If you put another copy somewhere else on the share that non of the other users are using, does the problem still exist?
– MikeAWood
Sep 4 '12 at 22:56
I'll check it... but the chances of file contention on that particular file I used for testing are extremely remote, since it was choose randomly from one of too many archived old processes.
– lvella
Sep 5 '12 at 0:31
contention might be related to the 10 client connection limits. Certainly worth a look. Is this a new issue or something that has always happened?
– MikeAWood
Sep 5 '12 at 0:55
People there said the problem was related to the new VoIP phone installed on every table, bridging the central switch and the workstation (supposedly interfering with the network), but tests made with and without the phone made no significant difference. If are there any other factors that caused the issue, I don't know.
– lvella
Sep 5 '12 at 1:05
|
show 1 more comment
If the "slowness" only happens in Excel, I would probably look closer at the XML file and make sure the interpreter in Excel isn't having trouble parsing the XML. Could be malformed or having some trouble reading it. Try opening the file in other applications like Notepad etc and see if the slowness issue still exists. FWIW, XP isn't a good platform for sharing files with that many (50) users as it is limited to 10 client connections. You could be running into some contention issues with the other clients trying to read the XML file as well. I don't think your issue is the size of the file, but rather what excel is doing with the file once it opens it. But that is just my thought. Try doing a CSV file dump and opening it up in Excel and see how long that takes.
answered Sep 4 '12 at 22:43
MikeAWoodMikeAWood
2,3811 gold badge8 silver badges13 bronze badges
First, I had it wrong, it is not XML, it is XLS... an ordinary XLS. Secondly, the file opens OK when local.
– lvella
Sep 4 '12 at 22:51
a 700K excel doc should be fine. a few more things to check. In computer management, under shared folders, check under sessions and open files. Looks to see how many users are attached in there. XLS really doesn't like to "share" files and have multiple copies opened remotely. It could just be simple file contention. If you put another copy somewhere else on the share that non of the other users are using, does the problem still exist?
– MikeAWood
Sep 4 '12 at 22:56
I'll check it... but the chances of file contention on that particular file I used for testing are extremely remote, since it was choose randomly from one of too many archived old processes.
– lvella
Sep 5 '12 at 0:31
contention might be related to the 10 client connection limits. Certainly worth a look. Is this a new issue or something that has always happened?
– MikeAWood
Sep 5 '12 at 0:55
People there said the problem was related to the new VoIP phone installed on every table, bridging the central switch and the workstation (supposedly interfering with the network), but tests made with and without the phone made no significant difference. If are there any other factors that caused the issue, I don't know.
– lvella
Sep 5 '12 at 1:05
|
show 1 more comment
If the "slowness" only happens in Excel, I would probably look closer at the XML file and make sure the interpreter in Excel isn't having trouble parsing the XML. Could be malformed or having some trouble reading it. Try opening the file in other applications like Notepad etc and see if the slowness issue still exists. FWIW, XP isn't a good platform for sharing files with that many (50) users as it is limited to 10 client connections. You could be running into some contention issues with the other clients trying to read the XML file as well. I don't think your issue is the size of the file, but rather what excel is doing with the file once it opens it. But that is just my thought. Try doing a CSV file dump and opening it up in Excel and see how long that takes.
answered Sep 4 '12 at 22:43
MikeAWoodMikeAWood
2,3811 gold badge8 silver badges13 bronze badges
If the "slowness" only happens in Excel, I would probably look closer at the XML file and make sure the interpreter in Excel isn't having trouble parsing the XML. Could be malformed or having some trouble reading it. Try opening the file in other applications like Notepad etc and see if the slowness issue still exists. FWIW, XP isn't a good platform for sharing files with that many (50) users as it is limited to 10 client connections. You could be running into some contention issues with the other clients trying to read the XML file as well. I don't think your issue is the size of the file, but rather what excel is doing with the file once it opens it. But that is just my thought. Try doing a CSV file dump and opening it up in Excel and see how long that takes.
answered Sep 4 '12 at 22:43
MikeAWoodMikeAWood
2,3811 gold badge8 silver badges13 bronze badges
answered Sep 4 '12 at 22:43
MikeAWoodMikeAWood
2,3811 gold badge8 silver badges13 bronze badges
answered Sep 4 '12 at 22:43
MikeAWoodMikeAWood
2,3811 gold badge8 silver badges13 bronze badges
answered Sep 4 '12 at 22:43
MikeAWoodMikeAWood
2,3811 gold badge8 silver badges13 bronze badges
2,3811 gold badge8 silver badges13 bronze badges
First, I had it wrong, it is not XML, it is XLS... an ordinary XLS. Secondly, the file opens OK when local.
– lvella
Sep 4 '12 at 22:51
a 700K excel doc should be fine. a few more things to check. In computer management, under shared folders, check under sessions and open files. Looks to see how many users are attached in there. XLS really doesn't like to "share" files and have multiple copies opened remotely. It could just be simple file contention. If you put another copy somewhere else on the share that non of the other users are using, does the problem still exist?
– MikeAWood
Sep 4 '12 at 22:56
I'll check it... but the chances of file contention on that particular file I used for testing are extremely remote, since it was choose randomly from one of too many archived old processes.
– lvella
Sep 5 '12 at 0:31
contention might be related to the 10 client connection limits. Certainly worth a look. Is this a new issue or something that has always happened?
– MikeAWood
Sep 5 '12 at 0:55
People there said the problem was related to the new VoIP phone installed on every table, bridging the central switch and the workstation (supposedly interfering with the network), but tests made with and without the phone made no significant difference. If are there any other factors that caused the issue, I don't know.
– lvella
Sep 5 '12 at 1:05
|
show 1 more comment
First, I had it wrong, it is not XML, it is XLS... an ordinary XLS. Secondly, the file opens OK when local.
– lvella
Sep 4 '12 at 22:51
a 700K excel doc should be fine. a few more things to check. In computer management, under shared folders, check under sessions and open files. Looks to see how many users are attached in there. XLS really doesn't like to "share" files and have multiple copies opened remotely. It could just be simple file contention. If you put another copy somewhere else on the share that non of the other users are using, does the problem still exist?
– MikeAWood
Sep 4 '12 at 22:56
I'll check it... but the chances of file contention on that particular file I used for testing are extremely remote, since it was choose randomly from one of too many archived old processes.
– lvella
Sep 5 '12 at 0:31
contention might be related to the 10 client connection limits. Certainly worth a look. Is this a new issue or something that has always happened?
– MikeAWood
Sep 5 '12 at 0:55
People there said the problem was related to the new VoIP phone installed on every table, bridging the central switch and the workstation (supposedly interfering with the network), but tests made with and without the phone made no significant difference. If are there any other factors that caused the issue, I don't know.
– lvella
Sep 5 '12 at 1:05
First, I had it wrong, it is not XML, it is XLS... an ordinary XLS. Secondly, the file opens OK when local.
– lvella
Sep 4 '12 at 22:51
First, I had it wrong, it is not XML, it is XLS... an ordinary XLS. Secondly, the file opens OK when local.
– lvella
Sep 4 '12 at 22:51
a 700K excel doc should be fine. a few more things to check. In computer management, under shared folders, check under sessions and open files. Looks to see how many users are attached in there. XLS really doesn't like to "share" files and have multiple copies opened remotely. It could just be simple file contention. If you put another copy somewhere else on the share that non of the other users are using, does the problem still exist?
– MikeAWood
Sep 4 '12 at 22:56
a 700K excel doc should be fine. a few more things to check. In computer management, under shared folders, check under sessions and open files. Looks to see how many users are attached in there. XLS really doesn't like to "share" files and have multiple copies opened remotely. It could just be simple file contention. If you put another copy somewhere else on the share that non of the other users are using, does the problem still exist?
– MikeAWood
Sep 4 '12 at 22:56
I'll check it... but the chances of file contention on that particular file I used for testing are extremely remote, since it was choose randomly from one of too many archived old processes.
– lvella
Sep 5 '12 at 0:31
I'll check it... but the chances of file contention on that particular file I used for testing are extremely remote, since it was choose randomly from one of too many archived old processes.
– lvella
Sep 5 '12 at 0:31
contention might be related to the 10 client connection limits. Certainly worth a look. Is this a new issue or something that has always happened?
– MikeAWood
Sep 5 '12 at 0:55
contention might be related to the 10 client connection limits. Certainly worth a look. Is this a new issue or something that has always happened?
– MikeAWood
Sep 5 '12 at 0:55
People there said the problem was related to the new VoIP phone installed on every table, bridging the central switch and the workstation (supposedly interfering with the network), but tests made with and without the phone made no significant difference. If are there any other factors that caused the issue, I don't know.
– lvella
Sep 5 '12 at 1:05
People there said the problem was related to the new VoIP phone installed on every table, bridging the central switch and the workstation (supposedly interfering with the network), but tests made with and without the phone made no significant difference. If are there any other factors that caused the issue, I don't know.
– lvella
Sep 5 '12 at 1:05
|
show 1 more comment
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f424341%2fnetwork-behavior-of-slow-windows-shared-storage%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
You should take a trace with Wireshark to be able to see what is actually being waited for. I would suspect locking issues.
– the-wabbit
Sep 4 '12 at 23:10