[Samba] Samba Tuning

Jeremy Allison jra at samba.org
Wed May 15 16:32:02 GMT 2002


On Wed, May 15, 2002 at 02:07:48PM -0700, Adam Cormany wrote:
> The application is an application that my company has
> written. I'm noticing this when I am switching from
> one menu to another menu. During this switch, we are
> transferring images(averaging around 2-3k each, around
> 30 images on each load), some binaries, and some
> database work is being done. We know that on the
> redhat 7.3 side, the database activity is faster, but
> the networking seems to be the dragging point.
> 
> What I've done is make a networking mapping on my
> Windows 2000 Professional(X:\ ,not that it matters the
> letter). The X:\ drive mapping is to a filesystem
> (/ssinc in smb.conf) on our Redhat 7.3 system that has
> our images, binaries/executables, database, etc. What
> our program does then is to set a PATH to that
> drive(X:\) and downloads the images when the menu is
> being displayed. 
> 
> To display this menu on Windows 2000 Server as the
> server and Windows 2000 Professional as the client,
> the menu is fully displayed in 3 seconds.
> 
> To display this menu on Redhat 7.3 Server+Samba 2.2.4
> and Windows 2000 Professional as the client, the menu
> is fully displayed in 6 seconds.
> 
> I hope this explains it a little better than before.
> If you need anymore information please ask.
> 
> Below is my smb.conf as of now. I've made multiple
> modifications trying to gain performance so this is
> what I have at this minute:
> 
> # Samba config file created using SWAT
> # from 192.168.1.66 (192.168.1.66)
> # Date: 2002/05/15 15:33:52
> 
> # Global parameters
> [global]
>         workgroup = SSINC
>         server string = Samba %v on %h
>         security = DOMAIN
>         encrypt passwords = Yes
>         password server = *
>         username map =
> /usr/local/samba/private/usermap
>         log file = /usr/local/samba/logs/%m.log
>         max log size = 1000
>         large readwrite = Yes
>         change notify timeout = 300
>         socket options = TCP_NODELAY SO_SNDBUF=8576
> SO_RCVBUF=8576
>         wins proxy = Yes
>         wins server = 192.168.1.2
>         guest account = arkuser
>         admin users = acormany
>         oplocks = No
>         level2 oplocks = No

You have turned off oplocks - this is almost certainly
the problem. Remove the two lines :

>         oplocks = No
>         level2 oplocks = No

and re-test. I'm CC:ing this to the main Samba list as
most performance discussions go on there.

Jeremy




More information about the samba mailing list