WIP

mtojek · mtojek · commit 4721204d8379 · 2024-03-13T10:35:02.000+01:00
diff --git a/docs/admin/architectures/2k-users.md b/docs/admin/architectures/2k-users.md
@@ -21,26 +21,14 @@ enabling it for deployment reliability.
 | ----------- | -------------------- | -------- | --------------- | ----------- | ----------------- |
 | Up to 2,000 | 4 vCPU, 16 GB memory | 2        | `n1-standard-4` | `t3.xlarge` | `Standard_D4s_v3` |
 
-### Workspace nodes
-
-| Users       | Node capacity        | Replicas | GCP              | AWS          | Azure             |
-| ----------- | -------------------- | -------- | ---------------- | ------------ | ----------------- |
-| Up to 2,000 | 8 vCPU, 32 GB memory | 2        | `t2d-standard-8` | `t3.2xlarge` | `Standard_D8s_v3` |
-
-TODO
-
-Max pods per node 256
-
-Developers for up to 2000+ users architecture are in 2 regions (a different
-cluster) and are evenly split. In practice, this doesn’t change much besides the
-diagram and workspaces node pool autoscaling config as it still uses the central
-provisioner. Recommend multiple provisioner groups for zero-trust and
-multi-cloud use cases.
-
 ### Provisioner nodes
 
 TODO
 
+In practice, this doesn’t change much besides the diagram and workspaces node
+pool autoscaling config as it still uses the central provisioner. Recommend
+multiple provisioner groups for zero-trust and multi-cloud use cases.
+
 For example, to support 120 concurrent workspace builds:
 
 - Create a cluster/nodepool with 4 nodes, 8-core each (AWS: `t3.2xlarge` GCP:
@@ -49,3 +37,19 @@ For example, to support 120 concurrent workspace builds:
   (`CODER_PROVISIONER_DAEMONS=30`)
 - Ensure Coder's [PostgreSQL server](./configure.md#postgresql-database) can use
   up to 2 cores and 4 GB RAM
+
+### Workspace nodes
+
+| Users       | Node capacity        | Replicas | GCP              | AWS          | Azure             |
+| ----------- | -------------------- | -------- | ---------------- | ------------ | ----------------- |
+| Up to 2,000 | 8 vCPU, 32 GB memory | 128      | `t2d-standard-8` | `t3.2xlarge` | `Standard_D8s_v3` |
+
+**Assumptions**:
+
+- Workspace user needs 2 GB memory to perform
+
+**Footnotes**:
+
+- Maximum number of Kubernetes pods per node: 256
+- Nodes can be distributed in 2 regions, not necessarily evenly split, depending
+  on developer team sizes
diff --git a/docs/admin/architectures/index.md b/docs/admin/architectures/index.md
@@ -182,7 +182,7 @@ Database:
 
 ## Hardware recommendation
 
-### Control plane
+### Control plane: coderd
 
 To ensure stability and reliability of the Coder control plane, it's essential
 to focus on node sizing, resource limits, and the number of replicas. We
@@ -234,7 +234,19 @@ We recommend disabling the autoscaling for `coderd` nodes. Autoscaling can cause
 interruptions for user connections, see [Autoscaling](../scale.md#autoscaling)
 for more details.
 
-### Workspaces
+### Control plane: provisionerd
+
+TODO
+
+#### Scaling formula
+
+TODO
+
+**Node Autoscaling**
+
+TODO
+
+### Data plane: Workspaces
 
 To determine workspace resource limits and keep the best developer experience
 for workspace users, administrators must be aware of a few assumptions.
