Super_Spartan 56 Posted April 25, 2016 Share Posted April 25, 2016 (edited) Finally, you have managed to bring back the days of the light NOD32 v2, look at the benchmarks of before and after. Mind you, in wPRIME, the lower the time, the better, but that is a very small fraction of a second hit whereas with other AVs the hit is higher at around an increase of 0.5 to 1.5 seconds on the time needed by wPRIME to run the test Edited April 25, 2016 by Phoenix Link to comment Share on other sites More sharing options...
Administrators Marcos 5,274 Posted April 25, 2016 Administrators Share Posted April 25, 2016 I think this is caused by a small change that affected only benchmarks, not real-world use. Link to comment Share on other sites More sharing options...
Super_Spartan 56 Posted April 25, 2016 Author Share Posted April 25, 2016 I think this is caused by a small change that affected only benchmarks, not real-world use. if you notice my sig, I have the 950 Pro. Remember that user who complained about slow performance with the 950 Pro? https://forum.eset.com/topic/7072-nod32-90318-slows-down-samsung-pro950-per-magician-benchmark/ Never experienced that but it's working perfectly with NOD32 v10 I submitted a recommendation to the ESET Team: Please allow multiple location exclusions like in Avast Antivirus. I don\'t want to go to C:\\Program Files again and again to add different program folders one by one that I want to be excluded. Can you please make the exclusions interface a checkbox list so we can select multiple locations simultaneously? Link to comment Share on other sites More sharing options...
21jags 0 Posted April 25, 2016 Share Posted April 25, 2016 yes there was issue with earlier version (Specially with samsung magician) I had received a reply from ESET "The issue seems to be in mixing of cached and non-cached reads on a file. SSD benchmark does non-cached reads whereas we do cached read(s). Once there was at least one cached read on a file, subsequent non-cached reads need to flush/purge cache which adds some small overhead on every read. If there is fair amount of reads, this small overhead can become significant." Link to comment Share on other sites More sharing options...
Recommended Posts