Hello, > SecuriteInfo db Speed... > > javascript.ndb: 9079 ms > securiteinfo.hdb: 2969 ms > securiteinfoascii.hdb: 1250 ms > securiteinfohtml.hdb: 2500 ms > spam_marketing.ndb: 1172 ms > > SecuriteInfo db memory use: > > javascript.ndb loaded > LibClamAV debug: pool memory used: 20.206 MB > > securiteinfo.hdb loaded > LibClamAV debug: pool memory used: 65.613 MB > > securiteinfoascii.hdb loaded > LibClamAV debug: pool memory used: 7.581 MB > > securiteinfohtml.hdb loaded > LibClamAV debug: pool memory used: 53.777 MB > > spam_marketing.ndb loaded > LibClamAV debug: pool memory used: 5.296 MB
Thank you for the benchmarks Steve. We are aware of this problem. With more than 1 million signatures, it takes too much ram/cpu on lower hardware systems. ATM, we mainly focus on javascript.ndb and securiteinfohtml.hdb to create more generic signatures. It will speed up database reload and increase detection ratio. Anyway, the best thing you should do is to increase RAM on your system, because every day official Clamav databases are growing, so one day you will get this problem even if you only use official Clamav databases. Furthermore, I think this is a bad idea to lower detection ratio due to a hadware limitation. -- Best regards, Arnaud Jacques SecuriteInfo.com Facebook : https://www.facebook.com/pages/SecuriteInfocom/132872523492286 Twitter : https://twitter.com/SecuriteInfoCom _______________________________________________ Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
