mirror of
https://github.com/coder/coder.git
synced 2026-09-24 15:04:27 +08:00
Spike Curtis
d5bb1361e2
Removes references to adding database replicas from the scaling docs, as Coder only allows a single connection URL. These passages where added in error.
3.1 KiB
3.1 KiB
Reference Architecture: up to 3,000 users
The 3,000 users architecture targets large-scale enterprises, possibly with on-premises network and cloud deployments.
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.
Observability: Deploy monitoring solutions to gather Prometheus metrics and visualize them with Grafana to gain detailed insights into infrastructure and application behavior. This allows operators to respond quickly to incidents and continuously improve the reliability and performance of the platform.
Hardware recommendations
Coderd nodes
| Users | Node capacity | Replicas | GCP | AWS | Azure |
|---|---|---|---|---|---|
| Up to 3,000 | 8 vCPU, 32 GB memory | 4 node, 1 coderd each | n1-standard-4 |
m5.xlarge |
Standard_D4s_v3 |
Provisioner nodes
| Users | Node capacity | Replicas | GCP | AWS | Azure |
|---|---|---|---|---|---|
| Up to 3,000 | 8 vCPU, 32 GB memory | 8 nodes, 30 provisioners each | t2d-standard-8 |
c5.2xlarge |
Standard_D8s_v3 |
Footnotes:
- An external provisioner is deployed as Kubernetes pod.
- It is strongly discouraged to run provisioner daemons on
coderdnodes at this level of scale. - Separate provisioners into different namespaces in favor of zero-trust or multi-cloud deployments.
Workspace nodes
| Users | Node capacity | Replicas | GCP | AWS | Azure |
|---|---|---|---|---|---|
| Up to 3,000 | 8 vCPU, 32 GB memory | 256 nodes, 12 workspaces each | t2d-standard-8 |
m5.2xlarge |
Standard_D8s_v3 |
Footnotes:
- Assumed that a workspace user needs 2 GB memory to perform
- Maximum number of Kubernetes workspace pods per node: 256
- As workspace nodes can be distributed between regions, on-premises networks and cloud areas, consider different namespaces in favor of zero-trust or multi-cloud deployments.
Database node
| Users | Node capacity | Storage | GCP | AWS | Azure |
|---|---|---|---|---|---|
| Up to 3,000 | 8 vCPU, 32 GB memory | 1.5 TB | db-custom-8-30720 |
db.m5.2xlarge |
Standard_D8s_v3 |
Footnotes for AWS instance types:
- For production deployments, we recommend using non-burstable instance types,
such as
m5orc5, instead of burstable instances, such ast3. Burstable instances can experience significant performance degradation once CPU credits are exhausted, leading to poor user experience under sustained load.