[clamav-users] Clamd high CPU during clamdscan
jeffroeq at gmail.com
Wed Jan 27 09:41:55 EST 2016
I think I may be overreacting to a monitoring issue. The CPU utilization
stays around 100% and the load jumps up for around 30min and then drops
back down. Obviously this amount of time will vary, but as I roll this out
to the rest of the environment, I want to minimize the alerts coming out.
I was looking for any possible settings which could ease clamd's CPU use.
I've used ClamAV in other environments but I think monitoring was a little
more lenient for high CPU load for periods less than 60min.
On Wed, Jan 27, 2016 at 12:38 AM Dennis Peterson <dennispe at inetnw.com>
> The "nice" utility is your very best friend. It yields CPU time to other
> operations but will run like crazy of nothing else is a higher priority.
> Clam is
> a disk IO heavy process for obvious reasons, and can drive disk waits up
> high. It is also CPU intensive but should occupy a single core. There is
> no way
> around the disk IO problem because it scans files. But - if you run it just
> after a system backup chances are good it will find many of the files it
> in cache. That helps reduce disk IO but bumps up CPU load.
> On 1/26/16 10:26 AM, Jeff Johnson wrote:
> > I have rolled out clamd to a handful of Red Hat systems and they all seem
> > to have high CPU usage when clamdscan runs at 2am. The rest of the day,
> > clamd drops down to minimal usage. There isn't a lot of change on these
> > systems so I can't imagine it's finding much, but it really pegs the
> > What configuration settings could I change for clamd or clamdscan to not
> > hammer the CPU?
> > Thanks
> > _______________________________________________
> > Help us build a comprehensive ClamAV guide:
> > https://github.com/vrtadmin/clamav-faq
> > http://www.clamav.net/contact.html#ml
> Help us build a comprehensive ClamAV guide:
More information about the clamav-users