Slowdown of Microsoft Visual Studio due to different Virus scanner

I haven't really done any measurements, but what I usually do is to exclude the real time scanning of my development folder (usually my :\Projects folder). That way, the compiler can work as fast as possible during my everyday repetitive tasks. I do have a daily scan that have the folder in question in its path, in order to fetch any possible threat. On a subjective note, I prefer to use NOD32.

Based on previous installations at various jobs, empirically rated from slowest (very annoying) to quickest (almost no impact):

• Symantec (awful)
• McAfee
• AVG
• ESET
• Computer Associates (excellent)

I wouldn't bother with the speed tests, etc. shown at the AV review sites since most of these are in controlled environments, often with review-mode enabled. The impact will also vary depending on your network environment (workgroup or domain) and administrator-enforced policies.

Disclosure: I used to work on another now-obsolete anti-virus package back in the 90's.

I'd have to agree with the first answer.

I've seen such issues differ between jobs according to the verocity of the admins' intent to leave configs unchanged for devs. Correctly setup virus scanners still hinder dev, but at least it's bearable.

So I edit the scan lists to:

• Exclude all dev code directories
• Exclude Temporary ASP.Net gen'ed areas
• Exclude Resharper caches

I find this improves the disk thrashing that otherwise occurs with Visual Studio, Resharper and a Virus Scanner all hammering the drive. As always SysInternals' Filemon can help you target rogue services/processes.