Re: [Clamav-users] Clamav Memory/System requirements

[Shawn Bakhtiar]

ps -aux

...
clamav2716  0.0  4.1 222492 168760 ?   Ssl  May26   0:40 clamd
clamav2722  0.0  0.0  57540   784 ?Ssl  May26   0:00 clamav-milter
...


On a Prolient GL165 4 x Quad-Core AMD Opteron(tm) Processor 2352 with 4GIG of 
memory. Fedora release 8 (Werewolf), ClamAV 0.96.1/11089/Thu May 27 06:47:23 
2010.


The process has been running for a day on our resides on our smtp gateway 
server, along side SpamAssassin..




 From: cswi...@mac.com
 Date: Wed, 26 May 2010 15:27:05 -0700
 To: clamav-users@lists.clamav.net
 Subject: Re: [Clamav-users] Clamav Memory/System requirements
 
 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
  
_
The New Busy is not the old busy. Search, chat and e-mail from your inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_3
___
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml

Re: [Clamav-users] Clamav Memory/System requirements

[Chuck Swiger]

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