If you plan to use build, test, or release automation extensively, we recommend that you use higher-spec application and data tiers to avoid performance issues. A data tier with two or more quad-core processors, 16 GB or more of memory, and advanced high-performance storage, like an SSD or high-performance SAN.An application tier with one quad-core processor, 16 GB or more of memory, and a fast hard-disk drive.A data tier with one quad-core processor, 16 GB of memory, and high-performance storage, such as an SSD.ДЇor a team of more than 2,000 users, consider the following setup:.

An application tier with one dual-core processor, 8 GB of memory, and a fast hard-disk drive.

Extensive use of automated build, test, or releaseДЇor a team of more than 500 users, consider the following setup:.

The following scenarios might require a multiple-server deployment: This configuration isn't recommended for a production server that's used by more than one person. For example, increasing RAM to 8 GB should enable a single-server deployment to scale up to 500 users.ДЇor evaluation or personal use, you can use a basic configuration with as little as 2 GB of RAM. A scaled-up server can also use search or reporting features. When you scale up a single server, the server can handle a larger number of users and an increased use of automated build, test, or release.

We don't recommend use of search or reporting features for this configuration. Extensive use of automated build, test, or release likely will cause performance issues. This configuration typically supports up to 250 users of core source control (Team Foundation Version Control or Git) and work item tracking functionality. For Elastic Search, you should use two dual-core processors and 8 GB of RAM. Single-server deploymentДЄ single-server deployment consists of a single machine with one dual-core processor, 4 GB of RAM, and a fast hard-disk drive. All the machines that are described in the next sections can be either physical or virtual. For example, if you have particularly large Git repositories or Team Foundation version control (TVC) branches, you might need higher-spec machines than those listed in the following sections. Your requirements might vary depending on how your team uses Azure DevOps. The following recommendations apply to most Azure DevOps deployments. It can support high-use scenarios that have multiple application tiers behind a load balancer and multiple SQL instances that use SQL Always On. Azure Artifacts and version compatibilityДЄzure DevOps on-premises can scale from an Express installation on a laptop that's used by a single person to a highly available deployment that's used by thousands of people.Client and on-premises build compatibility.In addition to these requirements, review the following articles as well: Prior to installing or upgrading an Azure DevOps deployment, review the requirements provided in this article. Azure DevOps Server was previously named Visual Studio Team Foundation Server.

Microsoft team foundation server specs