-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/18/2007 03:26 PM, David F. Skoll wrote: > Steven Stern wrote: > >> After 3 1/2 hours >> 2332 clamav 20 0 216m 83m 1636 S 0 4.1 0:21.52 clamd >> It does seem to be growing > > That's probably perfectly normal. Clamd uses pthreads. When it needs > to allocate space for a new thread's stack, it allocates memory. > When the thread exits, the memory is not returned to the operating > system but is recycled. So you can expect clamd to grow, quickly at > first and then gradually, until it reaches some steady-state related to > the maximum number of threads that have ever run simultaneously. > > It's also the reason that clamd will appear to use a LOT more memory on > a busy server than on a quiet one. > > Now, as to whether pthreads vs. a traditional preforked UNIX server > was the right design decision... that's a whole other thread, so to > speak. :-) >
Memory usage seems to have stabilized after 24 hours. No big deal, I guess. - -- Steve -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFHacV1eERILVgMyvARAvt2AJ99ZCE11PERUojVQ8tJ5KlXTkUZZQCePniS cCwApItuvYfaM8N2+wm67/E= =Kz92 -----END PGP SIGNATURE----- _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
