It looks like my point was lost in the noise so I'll try to distill it.

I ran clamdscan twice on my /home (69k files) and got:
 
# clamdscan --fdpass /home
...
Time: 1428.433 sec (23 m 48 s)
# clamdscan --fdpass /home
...
Time: 1355.057 sec (22 m 35 s)
#

The cache only saved a little over a minute on a 24 minute scan.

But on /boot, with 342 files:

# clamdscan --fdpass /boot
...
Time: 21.186 sec (0 m 21 s)
# clamdscan --fdpass /boot
...
Time: 0.362 sec (0 m 0 s)
#

Here, on a much smaller scan, the cache made a huge difference. That
tells me that the cache isn't large enough to significantly speed up
large scans.

I don't see that the cache size is run-time configurable. Is that right?

-DaveĀ 

_______________________________________________

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Reply via email to