[Dovecot] dovecot process nice value
My imap processes seem to all be running with a nice value of -15 (top priority). Is this usual? Not sure if this is a dovecot setting or something going on with my own system configuration somewhere.
I know the userdb query can set the nice value but mine (a mysql query) does not...
We're having problems with our mail partition being absolutely thrashed and thought over-strong imap processes might be a factor.
Many thanks, Daniel
On Mon, 2007-12-03 at 13:05 +0000, Daniel Watts wrote:
My imap processes seem to all be running with a nice value of -15 (top priority). Is this usual? Not sure if this is a dovecot setting or something going on with my own system configuration somewhere.
Normally Dovecot doesn't touch processes' priorities, so they all run with whatever priority was specified for the master process when starting it.
Timo Sirainen wrote:
On Mon, 2007-12-03 at 13:05 +0000, Daniel Watts wrote:
My imap processes seem to all be running with a nice value of -15 (top priority). Is this usual? Not sure if this is a dovecot setting or something going on with my own system configuration somewhere.
Normally Dovecot doesn't touch processes' priorities, so they all run with whatever priority was specified for the master process when starting it.
Hi timo - thanks for this. The /usr/sbin/dovecot process itself was indeed niced to -15. Why would that be? Can dovecot specify it's own nice value upon startup? When you say 'specified for the master process' I'm not sure if you mean in a config somewhere.
Thanks, Dan
-- Running Squirrelmail 1.5.2 in Production PHP 5.x Hardened with Eaccelerator Apache 2.x Mysql 5.0.x Imapproxy over Dovecot/Maildir all running on Gentoo Linux for ~5,000 users.
On Mon, 2007-12-03 at 16:25 +0000, Daniel Watts wrote:
Timo Sirainen wrote:
On Mon, 2007-12-03 at 13:05 +0000, Daniel Watts wrote:
My imap processes seem to all be running with a nice value of -15 (top priority). Is this usual? Not sure if this is a dovecot setting or something going on with my own system configuration somewhere.
Normally Dovecot doesn't touch processes' priorities, so they all run with whatever priority was specified for the master process when starting it.
Hi timo - thanks for this. The /usr/sbin/dovecot process itself was indeed niced to -15. Why would that be? Can dovecot specify it's own nice value upon startup?
Nope.
When you say 'specified for the master process' I'm not sure if you mean in a config somewhere.
I meant whatever/however dovecot was started. I don't know if some init.d scripts play with priorities. Or it could have just been that your shell was running with -15 when starting dovecot.
Anyway, I don't think Dovecot itself should change its priority on startup.
Timo Sirainen wrote:
On Mon, 2007-12-03 at 16:25 +0000, Daniel Watts wrote:
Timo Sirainen wrote:
On Mon, 2007-12-03 at 13:05 +0000, Daniel Watts wrote:
My imap processes seem to all be running with a nice value of -15 (top priority). Is this usual? Not sure if this is a dovecot setting or something going on with my own system configuration somewhere. Normally Dovecot doesn't touch processes' priorities, so they all run with whatever priority was specified for the master process when starting it.
Hi timo - thanks for this. The /usr/sbin/dovecot process itself was indeed niced to -15. Why would that be? Can dovecot specify it's own nice value upon startup?
Nope.
When you say 'specified for the master process' I'm not sure if you mean in a config somewhere.
I meant whatever/however dovecot was started. I don't know if some init.d scripts play with priorities. Or it could have just been that your shell was running with -15 when starting dovecot.
Anyway, I don't think Dovecot itself should change its priority on startup.
Ok - you're probably right about my shell being reniced before startup. Will check that out. Thanks a lot for your time Timo. Just upgraded Dovecot to 1.0.7 as well. Looking good so far.
participants (2)
-
Daniel Watts
-
Timo Sirainen