[Dovecot] 0.99.10.x auth memory leak?
tss at iki.fi
Thu Jul 22 16:22:19 EEST 2004
On 22.7.2004, at 06:01, Christian Balzer wrote:
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
> 31235 root 16 0 220m 216m 5560 S 0.0 10.7 25:01.54
> 31234 root 16 0 205m 202m 5560 S 0.0 10.0 24:08.84
> 31231 root 16 0 200m 196m 5560 S 0.7 9.7 23:25.37
> 31232 root 16 0 196m 192m 5560 S 0.0 9.5 23:10.44
> 31233 root 15 0 179m 175m 5560 S 0.3 8.6 22:13.07
> So, I guess my questions to Timo are:
> Think it's leaky and any idea where?
I didn't see any obvious leaks in the code. 1.0-test's dovecot-auth can
be easily run standalon, so it's easier to check for leaks with it.
I'll try to setup LDAP server and see if I can find any.
How soon does the memory go that high up? Do you restart the processes
manually? Do they stay in around 200MB by themselves, or only because
max. auth process size is 256MB (by default) and they restart
themselves when they reach it (log should have "out of memory" errors)?
> Given the load, would a single auth process be a bad idea?
> (it is a quite fast dual opteron box)
In that process list they were taking less than 1% CPU, so reducing
them shouldn't make it slower. But I'd still leave two just in case one
of them gets stuck for some reason.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://dovecot.org/pipermail/dovecot/attachments/20040722/fe65acf5/PGP.pgp
More information about the dovecot