AFP/SMB Directory Listings very slow in Finder

I would like to add my 0,20 cents here:

Situation = (same issue here) MAVERICKS + WINDOWS 8.1 shares... very, very slow browsing.

(Gigabit switch, wired ethernet, RAID 0 on Windows 8.1 with 3HDs and RAID 1 on OSX with 2HDs)

So i decided to test two scenarios:

1) Using only cifs:\\ shares (smb1 on OSX) = a) browsing are really fast, but b) no transfers got more then 450Mbits either for lager files (more then 25Gb) or smaller files;

2) Using smb:\\ shares (smb2 on OSX now) = a) browsing like **** (5min to list 200 files), but all transfers toutched the ceilling here at 850Mbits to files larger than 12Gb and 980Mbits for files smaller than 12Gb (I think that files within the windows cache are faster);

I also tested some NAS providers over my corporate network and one specially designed to operate at 4Gbits speeds (FreeNAS with 6HDs plus two eth interfaces) gave me slow browing under Mavericks. It also had smb2 under the hood and browsing was signifcantly faster then windows 8.1, but really slower then previous OSX versions.

I will try touching the windows parameters here as well as shutting down the .DS files to see how far can my MBPro lands here.

Txns for tips!!!

Ok, the smb2 parameters did the trick here... it seems windows are quite conservative regarding client requests throttling up, so buffing up these parameters really worked here (might not be the case with VPNs or high latency links).

Just checked some smb2 guides and it is quite ok to change these parameters. Windows are more likely to use smb3 nowadays.

I will try to mimic these smb2 parameters with my NAS devices here and will post results when available.

Cheer up!

Experiencing the same issues as described by all. Devastatingly slow connectivity speed with Mavericks that has required we bring back older machines running Lion. Its unfortunate Apple will not respond to a show stopper situation that is so critical to their business customers. Here is an interesting fact. Connecting to an old XServe sitting in a Win Server environment running 10.6 offers the same fast afp connectivity from any OSX workstation. Lightning fast with Mavericks.

Westrex,

I truly believe this is related to SMB2 parameters in OSX 10.9. I tweaked some parameters in my Windows 2008 R2 server, matching the OSX 10.9 required behavior, and everything got blazing fast using SMB shares (SMB2) (around 960Mbits). I never used AFP for practical reasons, mostly because I have a few MacBooks here and SMB is the default connection (avoiding add another service to my servers).

Regard, that in my tests, SMB2 connections were far better (after the tweaks in the server side) than SMB1 (cifs://) connections, and besides the fast browsing files and folders, transfers were slow (below 400Mbits) using SMB1. I would try configuring the same parameters at your windows SMB2 servers so you could adjust to OSX 10.9 behavior that is more aggressive.

The parameters were:

"Smb2CreditsMin and Smb2CreditsMax

HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters\Smb2CreditsMin

HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters\Smb2CreditsMax

And I used the sweetcider method (powershell). Smb2CreditsMin set to 768 and Smb2CreditsMax set to 16384 (decimal values)

Great, I'll give it a go. I was always told to never use SMB for connection using a Mac to Win environment. We use a workaround using afp and Acronis ExtremeZ-IP. I suppose in this case the Win server will think it is, and negotiating like a PC. Just wondering if metadata in files and directories will behave the same or there will be some data loss from the files created in OSX. Thanks

My experience is also the same.

In the EMC guide, there's one step about calculating your appropriate values for net.inet.tcp.sendspace – TCP send buffer and net.inet.tcp.recvspace – TCP receive buffer. In it, they say you can calculate an appropriate value for your network using this formula: Total network bandwidth (in bytes/second) x roundtrip delay (in seconds) = approximate send/receive buffer (in bytes). For example, if you have a 1 Gbps network with 1 ms of end-to-end delay, an appropriate buffer value would be: 125,000,000 x 0.001 = 125,000 bytes.

To obtain the value to plug in for end to end delay, can you simply take the average result from running a ping test in the terminal between the client machine and the server or is there some other method you used to get this value?

Jorge,

Did you have to create the Smb2CreditsMin / Smb2CreditsMax registry keys? Looking at mine now, and they do not exist.

I used the powershell method (within this forum thread, see below) , all parameters where there... just typed the commands to change values. My windows version in this case is 8.1 Pro.

An alternative to using regedit for those uncomfortable messing with the registry is to user powershell SMB share cmdlets. It's really easy.

Bring up an administrative command prompt and type in powershell. At the resulting prompt, type in

get-smbserverconfiguration (it's all one word) and look up your current values for smb2creditsmin and smb2creditsmax. On Windows 8.1, mine were 128 and 2048 respectively.

Now type set-smbserverconfiguration -smb2creditsmin 512 -smb2creditsmax 8192 and respond Y to the confirmation prompt. Then just exit out of powershell and exit out of the command prompt.

Directory listings on the network share went from minutes to extremely quick.

Your tip really works, so I thought I'd share an easier way to do exactly what you suggested. Thanks!

Important: I had to reboot the windows machine after changing the parameters.

Jorge -

Thanks for the reply. I thought those changes were done server side vs a desktop client.

JohnJ15,

You are right... these parameters are "SERVER SIDE" (windows servers). In this case I was setting up win 8.1 home media shares. It appears to be something related to SMB2 -> OSX 10.9 on windows scenarios.

My tests with FreeNAS (bsd smb2 and smb3 implementation) and OSX 10.9 did not present the slow browsing behavior, although when browsing 3 or 4 thousand files folders I could notice slow browsing. In most scenarios OSX 10.9 file transfer performance were quite impressive, almost touch the ethernet and wifi ceilings

I also tested Win2k8 R2 shares, all with normal behavior.

I have also struggled with slow listing of Windows 2012 Server shares.

Wanted to post my solution to problem.

I was able to get it working as it should by installing trial version of Path Finder. Installed, removed, rebooted and now shares open fast also in Finder!

I'm Windows server guy and not so familiar with osx so if anyone knows how could we find out what does the Path Finder do that makes things work would be appreciated.

skihnia,

Path Finder is a program designed to connect to windows shares (but also to extend OSX files managing interface). I am quite sure it set up an environment in OSX to keep transfer within windows parameters (mimicking the explorer behavior).

Yes, That's why I installed and tried it in the first place. When testing I noticed that also Finder got better when Path Finder was installed. So now I would like to know what those parameters are that Path Finder changes in OSX so that it works with Windows shares.

I have seen and tried lots and lots of suggestions how to modify OSX but nothing seem to work well. At least not as well as after Path Finder install/uninstall.

Hi,

could someone who has a friend with a friend that has access to Yosemite perhaps peek over their shoulders when the connect with their 10.10 clients to AFP/SMB shares? If the behaviour stays the same or if Finder brings up the folder contents any faster?

that would be awesome....