A while back I had big problems with a client’s on-premise TFS environment suddenly running the CPU to near 100% for 2 – 5 minutes at a time. This slowed down the entire system and caused TFS to slow down to the extent that developers could not accomplish much on TFS. This happened intermittently and we took a few weeks to pin it down to the anti-virus. It seems TFS uses a local cache, and when you check out large repos (especially GIT repositories) it does a lot of churning and caching. The anti-virus insists on scanning each action and it starts to slow down the entire process.
I searched online and found some guidance around anti-virus exclusions, but I decided to add to it with a few of my opinions included of course.
Team Foundation Server
There are primarily 3 things that need to be excluded on the TFS server itself.
- W3wp.exe process. This is the Internet Information Services (IIS) worker process and is typically located here : C:\Windows\System32\inetsrv\w3wp.exe
- TFSJobAgent.exe process. This is the TFS background worker process and is typically located under the TFS install path under the “\Application Tier\TFSJobAgent” folder
- TFS file cache location. This is where we had issues. TFS does a lot of caching on the server, and uses this location to write it to disk. It is one of the configurations that is asked for during the install and you can see what it is if you open the TFS administration console under the “File Cache Location” property. The default location is “C:\TfsData\ApplicationTier\_fileCache”. You want to exclude on access scanning for this location.
TFS Build Machine
The TFS build machine may also take a bit of strain when it comes to the agent’s working directory. This may be a contentious discussion, because it is possible to have malicious code executed under this location. In your secure environment it may increase your build process slightly.
When the preceding exclusions are made, and you want to move to SQL, there is a pretty decent overview of what needs to be excluded here.
After we added these exclusions the TFS servers were humming along without any issues.