Discussion in 'other anti-virus software' started by testsoso, Nov 9, 2013.
how many disk read write does your antivirus produce?
never measured it but i can say avira and nod32 are amongst the lightest in this department.
not sure about least read/write ratio but:
Agnitum has one of the highest! i advice to stay away from it.
Emsisoft is very light and only read/writes when necessary.
Trend Micro has constant I/O access but the numbers are not high and disk access only when its scanning.
webroot and avast are the lowest that exist right now from a pure logical numbers basis.
what means i/o ? is this relayed to disk accesses?
avira free 2014:
i/o other bytes: 3.51 G
i/o read bytes: 3.75 G
i/o write bytes: 106 mb
win 7 64bit
your new ssd wont die due that...
Nod has really small write bytes. Only updates and some log files are written to disk.
Read bytes depend on your settings and your activity. But if you use SSD reading from disk does not wear it out.
I agree with @Brummelchen - no antivirus will wear out your SSD (if that is your concern).
Interesting. I'd be interested in seeing Webroot's average I/O usage in numbers.
I like your signature.
Does anyone know of any tests with actual numbers on this subject? I would like to see actual numbers but do not have time to do any testing myself.
Thanks, but I meant average numbers, from Webroot themselves.
I never found Avast that light in terms of disk i/o. Do you know custom settings?
NOD32 ESS v6. has much more i/o than avira. but lower in memory usage.
avira free's i/o usage stop to grow after an hour or so, that is interesting.
after an hour:
i/o read bytes: 4.65 G
i/o write bytes: 440 Mb
might be. all in all, your mileage may vary.
It's good and interesting with tests like these I think.
But you say "after and hour:" but an hour of what, web browsing, or heavy duty hard work?
I mean wouldn't it be best to have the PC do an automatic test task with each AV so that the AVs scan the same data in order to get an accurate I/O usage result. So that the testing conditions is equal to each product.
If you set only default extensions on all scanners and scan only files written to hdd (disable on access/execute) in Eset there will be very low disk usage.
Also Norton and WSA disk usage is very low cause their "whitelisting" works really good (turn off scheduled scans ofc).
I'm not sure what the standard way to measure I/O usage is but below is a pic from Task Manager to show the I/O stats for ZoneAlarm firewall and Qihu 360 IS processes taken one hour after my computer was last booted.
The read/write bytes in taskmgr encompass writes to disk, writes to network interfaces, write to system buffers, etc. In essence, it's an utterly irrelevant metric if you're specifically targeting writes to disk.
If you want to actually measure disk write impact, use resource monitor. Also, one surefire way to reduce AV app writes to disk is to disable logging.
That being said, write endurance on modern SSDs has improved to the point that, IMO, it's not really worth a tremendous amount of concern.
Yes, if that is the concern, I wouldn't be concerned. Most SSDs have a warranty beyond their useful life and if you are making backups as one should it really isn't an issue. My SSDs have been going for years with no problems and I do not baby them in the least.
webroot and other cloud av do not count because... they work in the cloud. nod32 is the lightest.
so far MSE has the lightest i/o usage.
Separate names with a comma.