Skip to content

docs: reorganize scaling docs #13574

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Jun 14, 2024
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
fix 404s
  • Loading branch information
ericpaulsen committed Jun 13, 2024
commit 241373bfe3cc7f7dbffea12c02edcb674a4fcfce
4 changes: 2 additions & 2 deletions docs/admin/provisioners.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,8 +21,8 @@ sometimes benefits to running external provisioner daemons:
[Scaling Coder](./scale.md#concurrent-workspace-builds) for more details.

Each provisioner can run a single
[concurrent workspace build](./scale.md#concurrent-workspace-builds). For
example, running 30 provisioner containers will allow 30 users to start
[concurrent workspace build](scaling/scale-testing.md#control-plane-provisionerd).
For example, running 30 provisioner containers will allow 30 users to start
workspaces at the same time.

Provisioners are started with the
Expand Down
10 changes: 5 additions & 5 deletions docs/admin/scaling/scale-testing.md
Original file line number Diff line number Diff line change
Expand Up @@ -90,11 +90,11 @@ Database:

## Available reference architectures

[Up to 1,000 users](1k-users.md)
[Up to 1,000 users](../architectures/1k-users.md)

[Up to 2,000 users](2k-users.md)
[Up to 2,000 users](../architectures/2k-users.md)

[Up to 3,000 users](3k-users.md)
[Up to 3,000 users](../architectures/3k-users.md)

## Hardware recommendation

Expand Down Expand Up @@ -153,8 +153,8 @@ with a deployment of Coder [workspace proxies](../workspace-proxies.md).
**Node Autoscaling**

We recommend disabling the autoscaling for `coderd` nodes. Autoscaling can cause
interruptions for user connections, see [Autoscaling](../scale.md#autoscaling)
for more details.
interruptions for user connections, see
[Autoscaling](scale-utility.md#autoscaling) for more details.

### Control plane: Workspace Proxies

Expand Down
2 changes: 1 addition & 1 deletion docs/admin/scaling/scale-utility.md
Original file line number Diff line number Diff line change
Expand Up @@ -249,6 +249,6 @@ an annotation on the coderd deployment.
## Troubleshooting

If a load test fails or if you are experiencing performance issues during
day-to-day use, you can leverage Coder's [Prometheus metrics](./prometheus.md)
day-to-day use, you can leverage Coder's [Prometheus metrics](../prometheus.md)
to identify bottlenecks during scale tests. Additionally, you can use your
existing cloud monitoring stack to measure load, view server logs, etc.
2 changes: 1 addition & 1 deletion docs/platforms/aws.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ We recommend keeping the default instance type (`t2.xlarge`, 4 cores and 16 GB
memory) if you plan on provisioning Docker containers as workspaces on this EC2
instance. Keep in mind this platforms is intended for proof-of-concept
deployments and you should adjust your infrastructure when preparing for
production use. See: [Scaling Coder](../admin/scale.md)
production use. See: [Scaling Coder](../admin/scaling/scale-testing.md)

Be sure to add a keypair so that you can connect over SSH to further
[configure Coder](../admin/configure.md).
Expand Down
2 changes: 1 addition & 1 deletion docs/platforms/gcp.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ We recommend keeping the default instance type (`e2-standard-4`, 4 cores and 16
GB memory) if you plan on provisioning Docker containers as workspaces on this
VM instance. Keep in mind this platforms is intended for proof-of-concept
deployments and you should adjust your infrastructure when preparing for
production use. See: [Scaling Coder](../admin/scale.md)
production use. See: [Scaling Coder](../admin/scaling/scale-testing.md)

<video autoplay playsinline loop>
<source src="https://github.com/coder/coder/blob/main/docs/images/platforms/gcp/launch.mp4?raw=true" type="video/mp4">
Expand Down
Loading