Bad performance with samba3
David.Collier-Brown at Sun.COM
Wed Feb 18 13:26:55 GMT 2004
Probbaly the best approach is to capture a log and a packet
trace from one of the slow opens. In the past we've seen
network problems slow down what shoud be fast servers like
To get a level-10 log for just one client machine,
use the tip in "Logging by individual client systems or users"
With logging turned to 10 on just one client, start
a packet capture with ethereal or the IBM utility of
choice, open one of the "slow" files, then stop
capturing and put the loggging back to normal.
A work of caution re packet captures: get the binary
capture, not one converted to ascii: the latter lose
If you have an ftp site, put the logs there and
drop us a line.
Raphael Berghmans wrote:
> On Tue, 2004-02-17 at 16:00, Fabien Chevalier wrote:
>>Le Mardi 17 Février 2004 15:46, Raphael Berghmans a écrit :
>>>Since our files server has been migrated from NT4 to Samba 3,
>>>several users complains that the time to open a Word or xls
>>>file is very long (about 30 seconds).
>>>Which could be the reasons of this bad performance ?
>>>Which parameters have to be modified ?
> Samba-3.0.0 - with 600 silmuntaneous smbd process
> IBM xseries 4-processor 2.8 Ghz, 1Gb RAM + 2Gb Swap, 1 Gigabit-Ethernet
> + SAN 400 Gb (fiber Channel 2Gbits/s)
> And most of the smb.conf options keep the default value.
> See you,
>>There are *a lot* of things that can make your samba server slow...
>>Give us some more piece of information(smb.conf, hardware type - new, old, same?),
>>and maybe somebody will be able to help you.
David Collier-Brown, | Always do right. This will gratify
Sun Microsystems, | some people and astonish the rest.
Toronto, Ontario, | -- Mark Twain
(905) 415-2849 or x52849 | davecb at canada.sun.com
More information about the samba-technical