the much better question is *why* is clamav that much memory wasting
especially 385 MB for the official rules which barely hit anything and
are removed here entirely from production machines for some weeks after
hit nothing over the last 3 months - any catches was done by
sanesecurity alone
that whole thing don't scale at all compared to any other AV solution
which runs fine on a win7 virtual machine with a total of 2 GB RAM
Am 02.02.2017 um 11:47 schrieb Groach:
Recently, following previous enquires, Steve @ Sane graced us with some
analysis on what typical memory usage was to be expected when using the
3 common signature databases (default, Sane and Securiteinfo). See the
original post here:
http://lists.clamav.net/pipermail/clamav-users/2016-December/003903.html.
In the thread there is a summary that reads:
Summary test:
Using clamscan only to scan test.eml (3,706 bytes)
ClamAV Official sigs only (daily/main):
pool memory used: 385.675 MB
Official + *all* Sanesecurity/Distributed sigs
pool memory used: 467.359 MB
Time: 39.500 sec (0 m 39 s)
Official + *all* Sanesecurity/Distributed + SecuriteInfo sigs
Time: 86.344 sec (1 m 26 s)
pool memory used: 750.292 MB
(seen here:
http://lists.clamav.net/pipermail/clamav-users/2016-December/003907.html
- dated december 2016)
These figures resonate with my system (running Clamd on windows platform).
However, we have a forum contributor that claims that his system those
signatures collectively run at 1.3GB usage.
(https://www.hmailserver.com/forum/viewtopic.php?p=192885#p192885). Can
anyone help explain why that would be or how to lower this memory
footprint
_______________________________________________
clamav-users mailing list
[email protected]
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/contact.html#ml
