Scan Time Has Increased Significantly With 3.0

[ritchie58]

My first scan using version 3.0 of just my (C:) drive (my other drives are protected by BitLocker encryption and I know are malware free) using a custom scan took well over 3 hours and it wasn't finished yet. I had to stop the scan because I had other things to do. The second scan, which was a complete scan of (C:), was a little faster at about 2 1/2 hours. If at all possible I think if you could increase the scanning speed a bit that would only be a good thing.

[mokito]

i have about 300/400GB of data and after 2h.30 it wasn't passed 6.000 files (with plus or clamav on). if used only on-line engines it was fast (+/- 1h.30 to scan 60.000 files i guess)

 

also check this:

 

http://www.youtube.com/languy99#p/u/0/9RnxfZL5hKs

 

VM with almost no software and it still is sluggish scan....

[alfred]

It is taking longer, but it's because it's doing more. The Clam engine (which I am assuming you have turned on) is actually tearing through installers, cab files, archives etc. and it's examining files types the cloud scanner does not. In short it's doing much more work. Having said that we are shipping a change in the last week of February which will increase scan speed times on containers (cab, msi's etc.) by about 30%.

 

al

[ritchie58]

That's what I figured was going on Al. With the Clam engine it was digging deeper into files which obviously will lead to more malware detections and that's good for the community as a whole. Look forward to the tweak on the container files. That should help quite a bit I bet. Thanks for getting back to me.