Geoff Posted November 28, 2007 Posted November 28, 2007 I have recently implemented a Linux/Samba/Cups/Pykota based print server. However I hit a problem with samba. There was very high CPU usage, mainly because of winbind and also hundreds of smbd processes. The root cause was that the server was keeping connections open to clients and waiting for the clients to drop the connection (a default setting in samba it seems). So I had to change the 'deadtime' global configuration option. I chose to use a setting of 5 (which means 5 minutes) before idle connections are dropped. This has reduced my 30+ load average to around 1.5
DMcCoy Posted November 28, 2007 Posted November 28, 2007 hmm, wonder if it affects OS X too. Although I should think I'd have to send out a search party to various retirement homes to find any people who worked on the version supplied with OS X
Geoff Posted November 28, 2007 Author Posted November 28, 2007 Maybe, it just seemed a silly to default to a setting that can cripple a samba server in a high workload enviroment. :/
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now