Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Speed up SMB (Samba) server performance' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Speed up SMB (Samba) server performance
Authored by: morgion on Mar 31, '04 10:15:30AM

Should these options be used instead of everything in the originial post, or should we still use "read size" and "getwd cache" as well as the new "socket options"?

That is, should we use the following:

read size = 1024
socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_SNDBUF=8576 SO_RCVBUF=8576
getwd cache = yes


[ Reply to This | # ]
Speed up SMB (Samba) server performance
Authored by: Anonymous on Mar 31, '04 11:49:08AM

I bumped the "read size" to 16384, as well. This value needs to be selected with some intelligence. I experimented with values like 4096, 8012 until things "felt" right. One should really measure the throughput properly when tweaking this value. See this Samba performance tuning reference. 16K is a pretty standard setting for BSD boxes.

I did not change the "getcwd cache" value from it's default .

According to Using Samba:

This global option specifies whether Samba should use a local cache for the Unix getwd() ( get current working directory) system call. You can override the default value of yes as follows:

[global] getwd cache = no

Setting this option to yes can significantly increase the time it takes to resolve the working directory, especially if the wide links option is set to no. You should normally not need to alter this option.

I've never noticed a problem accessing [homes] for any of my users.

[ Reply to This | # ]