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

johnstcn · web-flow · commit c67eba10d50c · 2024-05-23T10:00:23.000+01:00
diff --git a/docs/admin/architectures/index.md b/docs/admin/architectures/index.md
@@ -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
