Target load

coder · mtojek · Mar 15, 2024 · Mar 11, 2024 · Mar 12, 2024 · Mar 12, 2024
commit 894cddbcdffdc2dbeef64da39d1a5420acadf8cb
diff --git a/docs/admin/architectures/1k-users.md b/docs/admin/architectures/1k-users.md
@@ -4,6 +4,10 @@ The 1,000 users architecture is designed to cover a wide range of workflows.
 Examples of subjects that might utilize this architecture include medium-sized
 tech startups, educational units, or small to mid-sized enterprises.
 
+**Target load**: API: up to 180 RPS
+
+**High Availability**: non-essential for small deployments
+
 ## Hardware recommendations
 
 ### Coderd nodes

diff --git a/docs/admin/architectures/2k-users.md b/docs/admin/architectures/2k-users.md
@@ -8,8 +8,10 @@ seeking to accommodate their expanding user populations.
 Users can be evenly distributed between 2 regions or be attached to different
 clusters.
 
-The High Available mode is disabled in this setup, but administrators may
-consider enabling it.
+**Target load**: API: up to 300 RPS
+
+**High Availability**: The mode is _disabled_, but administrators may consider
+enabling it for deployment reliability.
 
 ## Hardware recommendations
 

diff --git a/docs/admin/architectures/3k-users.md b/docs/admin/architectures/3k-users.md
@@ -3,8 +3,11 @@
 The 3,000 users architecture targets large-scale enterprises, possibly with
 on-premises network and cloud deployments.
 
-Typically, such scale requires a fully-managed HA PostgreSQL service, and all
-Coder observability features enabled for operational purposes.
+**Target load**: API: up to 550 RPS
+
+**High Availability**: Typically, such scale requires a fully-managed HA
+PostgreSQL service, and all Coder observability features enabled for operational
+purposes.
 
 ## Hardware recommendations
 

diff --git a/docs/admin/architectures/index.md b/docs/admin/architectures/index.md
@@ -156,8 +156,8 @@ Coder:
 
 - Median CPU usage for _coderd_: 3 vCPU, peaking at 3.7 vCPU during dashboard
   tests.
-- Median API request rate: 350 req/s during dashboard tests, 250 req/s during
-  Web Terminal and workspace apps tests.
+- Median API request rate: 350 RPS during dashboard tests, 250 RPS during Web
+  Terminal and workspace apps tests.
 - 2000 agent API connections with latency: p90 at 60 ms, p95 at 220 ms.
 - on average 2400 Web Socket connections during dashboard tests.
 
@@ -205,10 +205,12 @@ this option enabled unless there are compelling reasons to disable it.
 
 Inactive users do not consume Coder resources.
 
-#### HTTP API
+#### HTTP API latency
 
 API latency/response time average number of HTTP requests
 
+depending on database perf
+
 TODO
 
 #### Scaling formula