More TODOs

mtojek · mtojek · commit 1a4dfb99bed5 · 2024-03-12T17:27:12.000+01:00
diff --git a/docs/admin/architectures/1k-users.md b/docs/admin/architectures/1k-users.md
@@ -19,3 +19,7 @@ tech startups, educational units, or small to mid-sized enterprises.
 ### Workspace nodes
 
 TODO
+
+### Provisioner nodes
+
+TODO
diff --git a/docs/admin/architectures/2k-users.md b/docs/admin/architectures/2k-users.md
@@ -23,10 +23,29 @@ enabling it for deployment reliability.
 
 ### 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
+
+For example, to support 120 concurrent workspace builds:
+
+- Create a cluster/nodepool with 4 nodes, 8-core each (AWS: `t3.2xlarge` GCP:
+  `e2-highcpu-8`)
+- Run coderd with 4 replicas, 30 provisioner daemons each.
+  (`CODER_PROVISIONER_DAEMONS=30`)
+- Ensure Coder's [PostgreSQL server](./configure.md#postgresql-database) can use
+  up to 2 cores and 4 GB RAM
diff --git a/docs/admin/architectures/index.md b/docs/admin/architectures/index.md
@@ -263,6 +263,8 @@ users.
 Mention that as users onboard, the autoscaling config should take care of
 ongoing workspaces
 
+0.25 cores and 256 MB per provisioner daemon
+
 ### Database
 
 PostgreSQL database
