Jump to content
EmanuelJac

Problem with using this product with clamav enabled.

Recommended Posts

Im not sure if its supposed to be like this, but enabling the clamav engine spikes the CPU and resource usage to 25% CPU and 350 megabytes of memory from 0-1% CPU and 50 megabytes of memory, is it always like this? the update button always says "up to date" even after reinstalling the product a lot of times and I have no folder that contains error logs.

Edited by EmanuelJac

Share this post


Link to post
Share on other sites

Hello EmanuelJac,

One of our most knowledgeable Administrators, Rob. Turner, just commented on why ClamAV might temporarily cause system resources to increase, here's what he had to say on the subject.

The clam av engine loads it's full virus definitions signature set into memory:  which takes from  100 to 600mb.  add to that the clam  scanning engine  and virus definitions updater and clam alone  can in a worst case  scenario use  in the the 700mb  of memory range.   Currently we have extra experimental blue keep preventative signatures out for a worm we're expecting that are inflating the  usual virus definitions set size.

You can try updating the clam av definitions set  via the update button in the gui and running a full scan overnight.  That might get you a smaller more concise set of definitions that'll take less memory  and get you over the initial performance hump of building the local cache up.

Share this post


Link to post
Share on other sites
6 hours ago, ritchie58 said:

Hello EmanuelJac,

One of our most knowledgeable Administrators, Rob. Turner, just commented on why ClamAV might temporarily cause system resources to increase, here's what he had to say on the subject.

The clam av engine loads it's full virus definitions signature set into memory:  which takes from  100 to 600mb.  add to that the clam  scanning engine  and virus definitions updater and clam alone  can in a worst case  scenario use  in the the 700mb  of memory range.   Currently we have extra experimental blue keep preventative signatures out for a worm we're expecting that are inflating the  usual virus definitions set size.

You can try updating the clam av definitions set  via the update button in the gui and running a full scan overnight.  That might get you a smaller more concise set of definitions that'll take less memory  and get you over the initial performance hump of building the local cache up.

That fixed it, altough the memory usage has now doubled and randomly spikes to 300 megabytes along with the cpu spiking to 25% sometimes

Edited by EmanuelJac

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...