WIP

mtojek · mtojek · commit bb268004c765 · 2024-03-15T11:52:31.000+01:00
diff --git a/docs/admin/architectures/2k-users.md b/docs/admin/architectures/2k-users.md
@@ -10,8 +10,8 @@ clusters.
 
 **Target load**: API: up to 300 RPS
 
-**High Availability**: The mode is _disabled_, but administrators may consider
-enabling it for deployment reliability.
+**High Availability**: The mode is _enabled_; multiple replicas provide higher
+deployment reliability under load.
 
 ## Hardware recommendations
 
diff --git a/docs/admin/architectures/3k-users.md b/docs/admin/architectures/3k-users.md
@@ -26,7 +26,8 @@ purposes.
 **Footnotes**:
 
 - An external provisioner is deployed as Kubernetes pod.
-- It is strongly discouraged to run provisioner daemons on `coderd` nodes.
+- It is strongly discouraged to run provisioner daemons on `coderd` nodes at
+  this level of scale.
 - Separate provisioners into different namespaces in favor of zero-trust or
   multi-cloud deployments.
 
diff --git a/docs/admin/architectures/index.md b/docs/admin/architectures/index.md
@@ -1,7 +1,7 @@
 # Reference Architectures
 
 This document provides prescriptive solutions and reference architectures to
-support successful deployments of up to 2000 users and outlines at a high-level
+support successful deployments of up to 3000 users and outlines at a high-level
 the methodology currently used to scale-test Coder.
 
 ## General concepts
@@ -168,7 +168,7 @@ Provisionerd:
 Database:
 
 - Median CPU utilization is 80%, with a significant portion dedicated to writing
-  metadata.
+  workspace agent metadata.
 - Memory utilization averages at 40%.
 - `write_ops_count` between 6.7 and 8.4 operations per second.
 
@@ -215,7 +215,9 @@ When determining scaling requirements, consider the following factors:
 - 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
-  gauge system usage and identify potential bottlenecks.
+  gauge system usage and identify potential bottlenecks. The number of proxied
+  connections: For a very high number of proxied connections, more memory is
+  required.
 
 **HTTP API latency**
 
