Mac os smb slow

Adjust SMB browsing behavior in macOS

In macOS High Sierra 10.13 and later, the default settings for browsing network folders such as Server Message Block (SMB) shares are ideal for most organizations and users. But you can make adjustments to optimize SMB browsing in enterprise environments.

This article is intended for enterprise and education system administrators.

Your Mac determines how each window and its contents should appear by collecting file information such as labels, tags, and other forms of metadata.

In macOS Sierra 10.12 and earlier, your Mac gathers all metadata for the files in a folder, compares it to the folder’s .DS_Store file, and then displays the folder’s contents. In macOS High Sierra 10.13 and later, this behavior is changed slightly: If a folder is sorted alphanumerically, the contents are displayed immediately, then the Finder collects and compares the rest of the folder’s metadata.

Speed up browsing on network shares

To speed up SMB file browsing, you can prevent macOS from reading .DS_Store files on SMB shares. This makes the Finder use only basic information to immediately display each folder’s contents in alphanumeric order. Use this Terminal command:

defaults write com.apple.desktopservices DSDontWriteNetworkStores -bool TRUE

Then log out of your macOS account and log back in.

To reenable sorting, use this command:

defaults write com.apple.desktopservices DSDontWriteNetworkStores -bool FALSE

Information about products not manufactured by Apple, or independent websites not controlled or tested by Apple, is provided without recommendation or endorsement. Apple assumes no responsibility with regard to the selection, performance, or use of third-party websites or products. Apple makes no representations regarding third-party website accuracy or reliability. Contact the vendor for additional information.

Источник

Question: Q: AFP/SMB Directory Listings very slow in Finder

Since the upgrade to OS X Mavericks we are experiencing server problems, browsing AFP/SMB shares on remote servers (VPN). The Directory Listing is very slow an can take up to 30 minutes for large listings.

Here’s the setup

• 2 networks are connected thanks to a VPN connection.
• All clients, in all connected networks can communicate to a common fileserver (MacPro with OS X 10.6 SnowLeopard Server) in Network A
• Firewall is not an issue between those networks
• The fileserver also has other network services set up (DNS, Mailserver, SMB, AFP, Firewall, . )
• The clients authenticate via OpenDirectory and Kerberos to the fileserver

So the problems occur if i want to connect a client on network B to the server on network A. Connection, authentication, . all good. Even the performance over the VPN, to tranfer files is OK. But browsing subfolders is catastrophic. I used AFP and SMB alike, results are the same.

I also made tests on older clients, to see if the fileserver is the problem. 10.6 and 10.8 clients can browse normally, speed is OK. Even Windows Clients can browse normally all the subfolders of the fileserver.

I analyzed different approaches made here, but none of them worked:

• Connect to share with explicit port
• Connect to share with FQDN
• Connect to share with port 445 (SMB)
• Setup an nsmb.conf with notify_off=yes
• .

I also did analyze different logs and there’s something i found, but can not say if it’s connected. I did see many log entries like this:

29.10.13 12:21:51,960 icbaccountsd[775]: -[ICBLocalDictionary writeLocalMapping:]: Status: Writing out local mapping to disk

29.10.13 12:21:51,960 icbaccountsd[775]: -[ICBLocalDictionary writeLocalMapping:]: Status: Ending writing out local mapping to disk

29.10.13 12:21:51,960 icbaccountsd[775]: -[ICBRemoteDictionary writeDevices]: Status: Writing out of devices

29.10.13 12:21:51,960 icbaccountsd[775]: -[ICBRemoteDictionary writeDevices]: Status: Ending writing out of device

I also saw tha a process «icbaccountsd» was often coming up an using all of my CPU, when i start browsing the share. Thus i could not find any documentation on it.

So my question: What can I do to accelerate the browsing of my AFP/SMB shares for all my Mavericks clients? What can I do to speed up the Directory Listing? And yes: i know about solutions like PathFinder, TotalFinder, . but i’m more interested in a native solution to this problem.

Источник

Question: Q: SMB Network Share Access slow (MAC OS X SL and Windows 2008 Server)

I’ve added some iMacs with 10.6 to the Active Directory. This works totally fine. Anyways, I have some trouble, when accessing shares on my network. I found out, that some problems came up, because my network name was XXX.XXX.local I changed the Domain name of the Active Directory, but still the problems exist:
When opening the finder, Open Office or Microsoft Word on the Mac and browsing through files and folders, it sometimes takes up to 30 seconds and more, until the content of a folder appears. I already tried ADmitMac from Thursby, but it didn’t seem to fix this problem. When accessing the shares from a Windows machine, they run pretty fast. Any idea?

Lenovo, Mac OS X (10.6.4)

Posted on Sep 6, 2010 6:04 AM

All replies

Loading page content

Page content loaded

Sep 12, 2010 3:01 AM

Sep 13, 2010 8:51 AM

thanks for answering.
I already renamed the whole domain to something like: intra.name.de

Also I changed the value in the second link. The access works, but it is sometimes frickin slow, espacially, when you are switching between folders.

Sep 16, 2010 6:13 AM

Sep 17, 2010 9:39 AM

Sep 19, 2010 8:14 AM

Sep 19, 2010 8:17 AM

You never said what this «Active Directory» server is? Is it 2003, 2008 or OS X Server 10.5.x or 10.6.X?

I have read some on sServer 2003 can speed up connections by implementing the setting fixes describe in the Microsoft article New registry entry for controlling the TCP Acknowledgment (ACK) behavior in Windows XP and in Windows Server 2003 and it Also helped 10.6 client users SMB speed. It might help if you have access to the Domain server machine.

Sep 19, 2010 6:08 PM

Sep 20, 2010 6:58 AM

it’s a Windows 2008 Std. Server. MAc OS X 10.6.4 Clients.
I have renamed the AD already 😉
The other suggestion you have made, I tried also.

Sep 21, 2010 10:52 AM

Sep 21, 2010 10:53 AM

I too have the exact same problem and need to figure it out soon. Very slow response times. It seems the server is getting over utilized (look at your resource monitor).

Current configuration are:
MAC OS 10.6.4 using a Windows 2008×64 as a file server. Clients are connecting via SMB.
Whats the common denominator here?
Our users are using Adobe InDesign 3. When users open the file located on the server and submits a print job directly to the printer, the InDesign links ( some files contain around 100 ) reach back to the server to reference the file before it prints. This may be why the server’s resources are heavily affected and may be the reason why it may cause slow response times for other MAC users who try and save, open or copy files from / to the server. We have not found a soultion and all things mentioned here including the internet links did not work. We are still testing other variables (copy the Indesign files locally to detemine if print times decrease, etc. Any comments appreciated.

Sep 28, 2010 4:34 PM

Okay. We found the solution. Extremez-IP, a thrid party tool that we installed on the server significantly reduced response times.

There is an incompatibilty with the basic SMB protocol MACS use to communicate with Windows. Essentially the amount of data genereated when MACs open a file ( as well as pull file info ) generate an extremely huge amount of traffic through SMB, and only the AFP protocol can effeciently pull the data across the two platforms without the server taking a performance hit if it was to pull the same data through SMB. Mainly OS X and above seem to be the most affected.

Message was edited by: shodazz

Sep 30, 2010 8:38 AM

Nov 15, 2010 6:35 PM

the extreme-ip tool didn’t fix the problem. But I will try connecting with the port.

Nov 16, 2010 7:17 AM

Nov 20, 2010 5:53 AM

Question: Q: SMB Network Share Access slow (MAC OS X SL and Windows 2008 Server) More Less

Источник

Fix for slow SMB access (smb security problem) with Mac OS X ( Vess R2600tiD and Sanlink2 10G )

Open this file: com.apple.smb.server.plist
Location: /Library/Preferences/SystemConfiguration/com.apple.smb.server.plist
Open the file with TextWrangler. (Free download at: http://www.barebones.com/support/textwrangler/updates.html)

Add this to the file:
SigningEnabled

SigningRequired

Restart the machine.
Hope this is helpful.

Not quite understand your question.

Could you talk more in detail?

The correct way to disable SMB Signing which is enabled by default on OS X 10.11.5 > 10.12 (Execute these instructions exactly):

To check that it properly wrote the nsmb.conf file:

Check if SMB signing is disabled on your share after you remount the SMB volume:

If you see the the SIGNING_ON = TRUE Variable, that means its still on and you did not execute the instructions properly.

This variable should not show up after you have disabled SMB signing on the OS X 10.11.5 client. This is also applicable for OS X 10.11.6>10.12 (Mac OS Sierra)

This variable should not show up after you have disabled SMB signing on the OS X 10.11.5 client. This is also applicable for OS X 10.11.6>10.12 (Mac OS Sierra)

This did not work for me. I tried it several times. Is there a keystroke missing or does this not work in Sierra? It would be nice to get the 10gbe Library Share for FCP 10.3 faster over smb.

«This did not work for me. I tried it several times. Is there a keystroke missing or does this not work in Sierra? It would be nice to get the 10gbe Library Share for FCP 10.3 faster over smb.»

This is applicable to macOS Sierra. I have prescribed this solution multiple customers.

1. Did you follow the instructions exactly and executed the above as root?
2. Did you remount the volume after the changes?
3. When you ran the command:

Does the SIGNING_ON variable equate to TRUE? It should not show up if the instructions were followed properly.

4. Have you benchmarked the speed of the SMB share before and after the changes? If so, what R/W speeds did you get?

If you need further assistance, please open a case at https://support.promise.com

«This did not work for me. I tried it several times. Is there a keystroke missing or does this not work in Sierra? It would be nice to get the 10gbe Library Share for FCP 10.3 faster over smb.»

This is applicable to macOS Sierra. I have prescribed this solution multiple customers.

1. Did you follow the instructions exactly and executed the above as root?
2. Did you remount the volume after the changes?
3. When you ran the command:

Does the SIGNING_ON variable equate to TRUE? It should not show up if the instructions were followed properly.

4. Have you benchmarked the speed of the SMB share before and after the changes? If so, what R/W speeds did you get?

If you need further assistance, please open a case at https://support.promise.com

I can confirm that my /etc/nsmb.conf file contains:

. and any SMB shares I mount show:

but do not show SIGNING_ON. However, my speeds are still less than ideal. I am not sure what else to do. I have been trying to fix this for months, to no avail.

This only signifies that SMB Signing is supported by the SMB server that hosts your shares.

1. What storage are you using for your SMB share(s)?
2. Does your 10Gb SANLink connect to a VLAN?
3. What are the R/W speed metrics that you’re receiving and what disk speed tool are you using to determine the speed?

Apple prescribes the same solution as the forum above:

Источник

Question: Q: Slow SMB/AFP share file listing

Got problem with SMB/AFP share. Have MB Pro and WD My Book Live NAS. With Windows computer and even Android phone everything works flawless, even R/W speeds are 4 times slover than on Mac. The setting is Mac via Wifi connected to Airport Extreme and WD My Book Live is wired to Airport Extreme. Getting R/W speeds 22/16 MB/s. BUT, when opening folders with 100+ files, than it hangs up for 10sec to even few minutes.

Tried these solution, but they didn’t work:

They were actual with 10.6, maybe in 10.8 somtehing has changed un workaround is something else.

Someone got ideas to fix that?

Thanks in advance!

MacBook Pro, OS X Mountain Lion (10.8.5)

Posted on Oct 15, 2013 9:41 AM

All replies

Loading page content

Page content loaded

Oct 15, 2013 1:07 PM

Allready have done this — none of them helped.

Oct 15, 2013 10:04 PM

Refer to the NAS vendor for support. I consider those devices to be toys, not serious networking equipment.

Oct 15, 2013 10:22 PM

NAS vendor forwarded me to Apple. And I believe that this is not NAS problem, as it only doesn’t work as intended with Mac OS. And second — it isn’t first problem with SMB in Mac OS, as You saw in these other posts.. so, I would think that IT IS MAC OS problem. I would even say that problem could be in Finder. One thing I noticed — it «hangs up» only when opening directory for the first time. Second time directory opens immediately. In first times it is generating some cache or something? (Thumbnails are disabled)

P.S.
This NAS is normal for home usage (I think so).

Oct 15, 2013 11:46 PM

Today took Mac to work, to see if it’s a NAS problem.

Tried to connect to few Samba servers and the situation is same — very slow file listing.

So — problem IS in MAC OS!

Oct 17, 2013 12:48 AM

A test you could try is file listing in Finder vs in Terminal using the «ls» command. Do «ls (directory)» on some directory with a lot of files, and check how long that takes. See if it’s slow in both or only slow in Finder.

If it’s only slow in Finder, it’s probably easier to fix. Maybe the .DS_STORE files are bad on both servers?

Oct 17, 2013 1:21 AM

ls — file listing was immediate (it showed only file names)

ls -l — file listing was slover as it had to get other properties like size, e.t.c.

As I undesrstand — Finder also shows information about size, date modified, e.t.c. — and that’s why it is slow. Am I right?

Oct 17, 2013 1:43 AM

Yeah, and load the icons. The point of the test is to isolate the file listing time. You said that ls -l was slower than ls, but how slow was it? Did it take longer than it should have? I would try ls -l vs Finder on some directory with a huge number of files that don’t have custom icons (so the icons don’t also have to download).

There might be a real way to test this by checking Finder’s network I/O usage, but I don’t know how.

Oct 17, 2013 9:45 AM

I would say so — if Finder would list items as fast as ls -l did, I wouldn’t complain.

It took some 2-3 seconds to list 400 file folder.

Источник