Jake wrote: |
To be compared with other antivirus available Free or commercial it is indeed very slow as i experience faster scan speed with avira and norton which i previously installed before. |
While I'm not a ClamWin developer, and haven't looked at the source code to see whether there's any way of speeding up the basic scanning algorithm, one thing which commercial products often do is to keep record of files they have previously scanned, their size, modification date, and (optionally) some sort of checksum which can be run really quickly, like MD-4. Then, rather than scan everything, they just look at their database to see if the file(s) concerned appear to be unchanged since the last scan. If so, they're skipped. Assuming that doing such a check is 10 times faster than just scanning, and that 90% of your files are unchanged between scans, it will only take 20% as long to do the second and subsequent scans. If you dare skip the checksumming, and only look at the file size and modification time, you could cut it down to more like 10%-11%. But this isn't a minor tweak, this would take someone quite a while to code into a Windows app. On a Unix/Linux system it would be a 20 minute scripting job, but I don't suppose that's any consolation...
A much simpler modification which might make you happy would be if ClamWin defaulted to running at the lowest possible priority. Then it would run slightly slower than it does now, but wouldn't interfere as much with your doing other things on your computer while it was running. Scans being lengthy isn't such a big deal when they aren't hogging most of the CPU + i/o bandwidth.