Hi, Alex-- On May 26, 2010, at 3:04 PM, Alex wrote: > Is it expected that clamd on Linux should take 315MB of RAM with a > normal configuration? The system is pretty busy, with clamdtop being > "IDLE" for no longer than two seconds at a time, with apparently three > instances running.
v0.96.1 clamd tends to run around 190MB during normal operation here under FreeBSD, and can drop back to around 120 MB if left completely idle. It also tends to bounce up to nearly 300MB for a brief period when a DB refresh happens, but it drops back to ~190MB pretty quickly > Is that 315MB an accurate representation, as reported by clamdtop, and > standard top? Probably. I gather that GNU's libc has deferred free() semantics when threading is in use, so it might not be freeing up memory as quickly as other C library implementations do. You might also check that you don't have both a main.cvd and main.cld, because that might cause two copies of the signatures to get loaded and nearly double the memory requirements.... > Is the memory requirements dependent upon the number of signatures, > databases, or otherwise? Mostly proportional to the # of signatures, which in my case is ~ 977401-- plus some more if you scan big files. Regards, -- -Chuck _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
