EmanuelJac Posted July 31, 2019 Report Share Posted July 31, 2019 (edited) 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 July 31, 2019 by EmanuelJac Link to comment Share on other sites More sharing options...
ritchie58 Posted August 2, 2019 Report Share Posted August 2, 2019 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. Link to comment Share on other sites More sharing options...
EmanuelJac Posted August 2, 2019 Author Report Share Posted August 2, 2019 (edited) 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 August 2, 2019 by EmanuelJac Link to comment Share on other sites More sharing options...
Ilgazc Posted October 10, 2019 Report Share Posted October 10, 2019 Laptops with light hardware and power needs lives a hardware resource nightmare with the Clamav issue in place. I don't know how powerful&effective Immunet is without Clamav enabled. I know Clamav isn't designed to be a great Windows AV (except mail servers) either. It would be nice if Clamav was an opt-in feature instead of opt-out. In current circumstances. Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now