Recently there have been internal discussions about the TFS Proxy and one of the engineers shared some information I thought would be useful to post:

Here are some of the best practices for TFS Proxy

 

  • Follow hardware recommendations in TFS install guide; specifically make sure that the proxy cache is deployed on a volume with lot of free disk space

 

  • Create a scheduled task to pull the latest files on a periodic basis to proxy. This will ensure that latest version of files are available in proxy cache and subsequent client requests for these files will result in cache hit

 

  • Proxy can be used even in high bandwidth environments. For instance if there are multiple teams using the same AT/DT and each team uses a separate Team Project then each such team can deploy a proxy. This will minimize (say CPU, Memory can be utilized for other tasks) the stress on AT/DT

 

  • Monitor Proxy Performance counters and event log (for errors/warnings) on a periodic basis, to get a good picture of how proxy is functioning

 

  • If large files are going to be downloaded over low bandwidth (< 3Mbps) network, then set executionTimeout to appropriate value in web.config (Default is 1hr - <httpRuntime executionTimeout="3600"/>)

 

 

For information about Team Foundation Server Proxy installation, see the Team Foundation Installation Guide available online at http://go.microsoft.com/fwlink/?linkid=40042  or the TFSInstall.chm file included with the product.

 

For information about Team Foundation Server Proxy configuration, refer to http://go.microsoft.com/fwlink/?linkid=62391 or in the product documentation.

 

For information about Team Foundation Server Topologies 

 

http://msdn2.microsoft.com/en-us/library/ms400668(VS.80).aspx

 

 

For more details on the TFS Proxy Server, Refer to the following screencasts.

 

http://go.microsoft.com/fwlink/?LinkId=62788