Team Foundation Server Proxy Requirements
Team Foundation Server Proxy is designed to boost network performance by caching copies of version controlled files in a remote location. This remote location is local to the developer needing the files, but is away from the main version control location. By storing copies in the remote location, the proxy helps each user avoid a download of the files to their workspace across the slower network connection. The Team Foundation Server Proxy manages that file cache for remote offices or for larger teams that want to improve performance in a large Team Foundation Server deployment by distributing some of the download activity away from the Team Foundation data-tier server. The server that is running the Team Foundation Server Proxy must meet the following requirements. The server should have a reliable network connection with a minimum bandwidth of 1 Mbps and a latency maximum of 350 ms.
Hardware Recommendations
Configuration |
CPU |
HD |
Memory |
Comments |
|---|---|---|---|---|
Standard |
1 processor, 2.2 GHz |
40 GB |
2 GB |
Used to support version control files for a remote team. |
Teams up to 2,200 users |
2 processors, 2.0 GHz |
73 GB |
2 GB |
Used to support large teams in a dual-server configuration. |
Teams between 2,200 and 3,600 users |
4 processors, 2.0 GHz |
73 GB |
2 GB |
Used to support very large teams in a dual-server configuration. |
See Also
Concepts
Team Foundation Server Planning Roadmap