#users experiencing slowness when saving excel files to network shares?

1 messages · Page 1 of 1 (latest)

zealous furnace
#

Hi there apparently it's not o365 related as the issue doesn't occur in the main location so i just used PSPing cmdline .\psping64.exe -i 1 -6 -w 10 -n 50s from 10.254.149.71: 16.97ms
Reply from 10.254.149.71: 16.70ms
Reply from 10.254.149.71: 49.17ms
Reply from 10.254.149.71: 16.90ms
Reply from 10.254.149.71: 55.42ms
Reply from 10.254.149.71: 16.44ms
Reply from 10.254.149.71: 16.58ms
Reply from 10.254.149.71: 17.12ms
Reply from 10.254.149.71: 15.29ms
Reply from 10.254.149.71: 16.89ms
Reply from 10.254.149.71: 16.90ms
Reply from 10.254.149.71: 72.98ms
Reply from 10.254.149.71: 16.74ms
Reply from 10.254.149.71: 16.79ms
Reply from 10.254.149.71: 15.95ms
Reply from 10.254.149.71: 15.76ms
Reply from 10.254.149.71: 17.74ms
Reply from 10.254.149.71: 17.59ms
Reply from 10.254.149.71: 16.51ms
Reply from 10.254.149.71: 16.77ms
Reply from 10.254.149.71: 16.87ms
Reply from 10.254.149.71: 15.45ms
Reply from 10.254.149.71: 20.87ms

Ping statistics for 10.254.149.71:
Sent = 41, Received = 41, Lost = 0 (0% loss),
Minimum = 15.12ms, Maximum = 72.98ms, Average = 20.14ms
PS C:\Users\JK44KN\Downloads\SysinternalsSuite> .\psping64.exe -i 1 -6 -w 10 -n 50s

#

is the 72.98ms slow and would kind of impact woulld that have, bare in mind its always takes 6 seconds to save a file maybe 7 seconds , but just 1 second if the file is saved locally or on onedrive

zealous furnace
#

but to be fair I ran a continous ping in realtime and its always arond 14.00ms to 15.00ms

warped zinc
#

Hi unfortuantely you've shard no information that anyone can actually use to help you.

#

You might want to consider sharing information like Model of your NetApp solution, Software version, what protocol is being used (CIFS, NFS, etc).

#

Given that ping is showing you are having network latency between you and whatever that ip address is, then its potentially a network issue inbetween your NetApp solution. That's obiously a very generalized guess based on the limited information you have provided. That network latency might be normal depending on where the IP address is located on your network.

#

Have you logged into your NetApp solution to check for any errors, warnings etc?

zealous furnace
#

I'll try and get more details as I'm a contractor with limited involvement, there is spreadsheet but it lacks any technical information just some basics it would seem the issue is specific to the Uk and the netapp shares are located in Holland - anyways I will get more info and post it here.

sturdy skiff
#

CIFS is very sensitive to slow networks (high latencies) because it uses many round-trips for its I/O, so the latencies quickly add up. Fixing the network latency will most probably reduce the impact. If this is a WAN, consider using a WAN accelerator appliance that can optimize CIFS, from our experience they are very good in improving responsiveness

zealous furnace
#

It's possible the issue reared it's head just around the time we implemented SD-WAN or when we finally moved everyone off domain based computers onto checkpoing vpn (intune devices) anyway they've said the fault doesn't occur in the main location and is specifically bad in the UK and terrible in another Eastern European country, 25 seconds to save a file, one thing I noticed if I try to load multiple excel sheets and pdfs my explorer.exe stops responding, I have collected logs but nothing obvious is showing so far. Lets see if i Pathping one of the DFS file shares directly and see if there's a latency issue between client and server

old dew
#

time to implement a flexcache solution, hehe

viral lake
#

Office is really picky about certain things, even the number of .lnk shortcuts in the folder.

#

If it's fine with Notepad, it's likely an Office/Windows/security software thing.

sturdy skiff
#

might be related to oplocks. I have heard reports that disabling oplocks speeds up access/latency sometimes (but I also heard the opposite, that enabling oplocks makes things faster, so YMMV but if you are looking for something to try, that could be one option)

zealous furnace
#

yeah looks like the manager is now getting the netapp team and others involved, though there's a lack of communication in this place as our infra teams elsewhere have a p1 with Microsoft , anyway one thing I've noticed is when excel opens a file from the network share it creates some tmp. files and a duplicate xls file locally in appdata/internet.MSO and when saving a tmp file is created and disappears on the network share, not sure if this is normal behaviour, will investigate, other than that I've run a wireshark capture and procmon capture using thiese funky Microsoft github scripts pretty mammoth and checked the SMB logs, I've sent all to the P1 global team head last week. also @sturdy skiff fair point on the Opslock, I'm coming in fresh as a local tech admin guy contracting here so I have no access to anything but didi come across this - ""

image.png
zealous furnace
#

I tried disabling OPlock through the registry on my machine though not sure if the server end also requires it, hasn't made a difference, oh well

coarse knoll
#

so my evidence is finally being added to the P3 ticket yeah! anyway it's hard to know if I have discovered anything that can help them resolve the issue, been advised that netapp have not found an issue, Microsoft haven't either lol so back to sqaure 1.

coarse knoll
#

so the issue existed before we moved to non-domained based systems so cant really blame the vpn connection either - anyway update from MS - bit of a joke really if you ask me but kinda understandable when you think about the saving process local and on network - During the months of investigating, we did together with Microsoft we have checked every single component we could (DFS, NetApp, network, client settings, Office and OS version), but at the end came to the conclusion that this is caused by latency in combination with the way how Office apps work (and always has worked). After talking to multiple users, we understood that this issue originated already on the old SWING platform but has gotten worse with every step we have made to the modern world. There are still components that are not migrated to the modern world like NetApp. When we migrated a dataset to SharePoint Online the issue did not appear anymore.

#

In combination with the statement of Microsoft that there is nothing they can do from their side (see below), we can only advice to speed up the migration to SPO. As a result, we will close the ticket.
Statement Microsoft Engineer:
I wanted to be certain of the Office versions, OS version and various network constraints before I can officially confirm our understanding about the time taken. I have been working on my lab which took longer then expected.

After various tests, I can confirm that with latency, office applications are bound to take time save files on the network where there is a latency. This is due to the design of the office application. The transactions that the office application does is to ensure that the user data is safe and thus there are multiple copies on both local and network device which provides ability of office applications to do auto recovery, on demand recovery etc.
Recover your Word files and documents - Microsoft Support
Open a document after a file corruption error - Microsoft Support
Save, back up, and recover a file in Microsoft Office - Microsoft Support

These features are present by default and are useful in case of accidental application close/crash or loss of the open file due to any other event. The downside to it is that this task requires a lot of network transactions for office, locally as well as remotely. If there is a latency in the network this will certainly add to the delay as we are observing. That said, all we can do in this issue is to try tweak a few things to optimize but that won’t be a drastic change thus there is no point in taking any further data/logs. This is a by-design behaviour of office application due to latency of the network.

viral lake
#

Interesting. What tweaks do they recommend?

coarse knoll
#

They don't they say that we need an infrastructure upgrade so basically they're saying they can't fix it and to move to sharepoint which we're doing anyway

#

Yeah the tweaks were nothing to outright fix the issue i forgot what the guy said in our team it was something to do with our onprem infra which we're slowly moving away from and it would require an overhall - but I can't but help wonder if they have purposly insured the slowndown on prem network files servers to sell sharepoint 365

old dew
#

ugh... sharepoint is pure evil... a kludge on top of the office kludge. Every re-organization leads to the same duplication of sharepoint instances so in the end, one has huge numbers of sharepoint instances that will live on forever because no one ever migrates "old data"

coarse knoll
#

What annoys me we have users who were on a 300ms latency to a global network share and the guys in Asia - their macros were failing with smb errors and vba errors on other occasions and it was taking over an hour to process a macro compared to say 10 minutes in the UK, though it would sometimes fail here too, I just dont get how albeit over a 2 year period a Corporate network is struggling , especially as we're well into the sharepoint migration you would think there would be less pressure on the existing netapp, really not impressed. Though as a contractor I know nothing here, no one includes me in anything, so damn them to hell.

old dew
#

hehe... storage is an afterthought... right in front of backup