On a Windows Server 2019 (Server Core) machine, after a minimal install (no search etc.) logging in with one user the total machine ram usage is already 6.2 GB. There's no way a 4 GB server can reliably serve 250 developers concurrently without performance issues.
Here's a screenshot of the top 4 processes by ram usage in task manager after logging in and creating the first project. There is nothing else running on this machine:
I'm aware SQL Server will be somewhat mindful of the maximum amount of RAM in the system, but I don't think it would stretch to allow 250 users to work without extreme slowdown due to swapping. In fact, our our production instance (which is only used for source control and code reviews) has trouble scaling to 30 users with 8 GB of ram available.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
ID: 4cf58945-edff-cb3b-ab71-d45d480f1044
Version Independent ID: 8a1c8ac9-a829-837b-5e52-81766c1f545e
On a Windows Server 2019 (Server Core) machine, after a minimal install (no search etc.) logging in with one user the total machine ram usage is already 6.2 GB. There's no way a 4 GB server can reliably serve 250 developers concurrently without performance issues.
Here's a screenshot of the top 4 processes by ram usage in task manager after logging in and creating the first project. There is nothing else running on this machine:
I'm aware SQL Server will be somewhat mindful of the maximum amount of RAM in the system, but I don't think it would stretch to allow 250 users to work without extreme slowdown due to swapping. In fact, our our production instance (which is only used for source control and code reviews) has trouble scaling to 30 users with 8 GB of ram available.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.