Running a FAS3270 Active-Active configuration providing NAS service via vFilers to multiple customers.
At the moment only CIFS is used, no NFS customers in this environment.
Some of our customers experience slow performance, some don´t.
I know this has been discussed several times, but this seems a little different.
If we test regular file copy we get very good result.
10-11 MB/s (90-95 Mbps) which is what the customers pays for.
But here´s the tricky part.
When they are trying to list files and folders in Explorer, the files won´t show all at the same time but it can take several seconds for all files to list.
Also saving a regular PPTX file (3 pages 1285kb) it takes several seconds for the folders to list when pressing 'Save as', then several more seconds to save it (the save bar comes up and shows a slow saving progress).
Also, if they create a folder inside a current share it takes a long time for the folder to show up.
Home folder is synced for offline use.
After restart of PC the problems seem non-existent, after a while the problem appears again.
So, could this be SMB issue?
Should we disable offline files on the folder ("cifs shares -change <sharename> -no_caching")?
Could disabling 8.3 filename support for the clients be helpful?
Could NOT using cifs homedir make for slow connection..I mean,does the SMB list metadata for the complete searchpath? (Exampel, user trying to save file to \\filer\users$\office1\group2\user\Documents\folder, does it list from users$ or from 'users' folder?)
Do you guys have any other experience where the filecopy speed is fine, but the user experience is slow??
I´ll specify them here first, and later I´ll link to all the KB´s and options I´ v found investigating this problem.
So it seems we had 2 issues here,
One on the client side, and one in the controller.
On the client side there was an issue with desktop.ini. As soon as a user would mapp their home folder the computer started to scan the entire folder structure for desktop.ini. Of course it got access deny on everyone (except its own). It also did 4 retries to be certian of its access. This caused 20-30 MS delay and with thousands of users with desktop.ini in the folders structure we got a huge delay. There is a KB on how to fix this from MS http://support.microsoft.com/kb/326549 , but our customer to another approach at this. As the desktop.ini file only function as a config file for the MS FilesSystem it´s not necessary, so the customer simply deleted all of them. Now, instead of 40-45 seconds to map a folder, it takes 0,5 seconds.
For our customer temp files as well as desktop.ini has been the biggest pain. Besides that he had some issues with appsense which i currently do not remember. Your best choise would be to do a network trace and analyze that one.Try colasoft capsa 7.
Yes, but not on NetApp systems. WAFL provides for writes to be instantly ACK'd the moment they hit NVRAM. Further, writes are coalesced prior to be sent to disk. NetApp is 180 degrees out from every other storage vendor on the subject of write performance and methodology.
Still, write needs to go into write cache and write log transactions hits the NVRAM, slower than just pump out data from read cache. Check netapp internal performance comparison reports, reads are always faster than write, even on netapp.
I have had issues for both for SnapMirror (opnly in one direction and on one filer being incredibly slow) and a few users not being able to even see CIFS shares where other users on same subnet next to them could.
The fix for this was ip.fastpath.enable being on, noiw the default. Chnaged to off and issues went away, ip.fastpath is not compatible with 10Gb networks when HSRP is in use, which it nearly always is.