synced/coder
1
0
Fork 0
mirror of https://github.com/coder/coder.git synced 2025-08-01 08:28:48 +00:00
Code Issues Packages Projects Releases Wiki Activity

chore: update scale docs to include guidelines for wsproxies (#13350)

Browse Source
This commit is contained in:
Cian Johnston
2024-05-23 10:00:23 +01:00
committed by GitHub
parent c2837a62e4
commit c67eba10d5
1 changed files with 11 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
docs/admin/architectures/index.md
View File

@@ -210,8 +210,9 @@ Inactive users do not consume Coder resources.
When determining scaling requirements, consider the following factors:
- `1 vCPU x 2 GB memory x 250 users`: A reasonable formula to determine resource
allocation based on the number of users and their expected usage patterns.
- `1 vCPU x 2 GB memory` for every 250 users: A reasonable formula to determine
resource allocation based on the number of users and their expected usage
patterns.
- API latency/response time: Monitor API latency and response times to ensure
optimal performance under varying loads.
- Average number of HTTP requests: Track the average number of HTTP requests to
@@ -239,6 +240,14 @@ We recommend disabling the autoscaling for `coderd` nodes. Autoscaling can cause
interruptions for user connections, see [Autoscaling](../scale.md#autoscaling)
for more details.
### Control plane: Workspace Proxies
When scaling [workspace proxies](../workspace-proxies.md), follow the same
guidelines as for `coderd` above:
- `1 vCPU x 2 GB memory` for every 250 users.
- Disable autoscaling.
### Control plane: provisionerd
Each external provisioner can run a single concurrent workspace build. For