[Pkg-samba-maint] Transition 3.0.14a-3sarge4 / 3.0.24-6
performance deterioration
Steve Langasek
vorlon at debian.org
Fri May 11 20:29:21 UTC 2007
Hi Johann,
On Fri, May 11, 2007 at 07:12:31PM +0200, Johann Zuschlag wrote:
> let me first thank you for your good work.
> While the upgrade from Woody to Sarge worked like a charm, unfortunately
> the last upgrade introduced a deterioration in performance. I never had
> to change my configuration file before. Of course I started checking
> every entry, did some changes, removed the additional entry for socket
> option except TCP_NODELAY. I deinstalled samba and reinstalled it again
> using the standard smb.conf. No change. Set TCP_NODELAY and switched off
> oplocks later. Same. I checked the network, changed the switch ports,
> still no change.
> I checked the samba mailing lists, but I couldn't find a reason for that
> behaviour.
> Since my users are all working on one database file I have to set
> oplocks to no. If I switch them on for testing, one client is very fast,
> but of course a second will break the oplocks and the speed will be down
> again. With Sarge the difference in speed is quite little. Maybe the new
> kernel behaves differently.
> I'm using the kernel 2.6.18 which came with Etch.
> Under Sarge the performance was very good, now everything is quite slow
> and the users are quite unhappy with me.
> Is there anything else I can do to improve performance? Maybe I did make
> a mistake. Any hints?
It would be best if you addressed these questions to the upstream support
list. Debian does not make any changes to the Samba software when packaging
it which should affect performance, and asking upstream will put you in
touch with a larger group of experts with broader experience in such
matters.
Cheers,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
vorlon at debian.org http://www.debian.org/
More information about the Pkg-samba-maint
mailing list