Skip to content

docs: use scale testing utility #12643

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 23 commits into from
Mar 22, 2024
Merged
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
WIP
  • Loading branch information
mtojek committed Mar 22, 2024
commit d1b0ddca5ea9fc145add37908c3adafbf997412e
12 changes: 6 additions & 6 deletions docs/admin/scale.md
Original file line number Diff line number Diff line change
Expand Up @@ -156,13 +156,13 @@ Scale testing concurrency can be controlled with the following parameters:

### Kubernetes cluster

Depending on the traffic projections, operators can deploy different sample
clusters to perform scale tests. It is recommended to learn how to operate the
scaletest-runner before running it against the staging cluster (or production at
your own risk).
It is recommended to learn how to operate the _scaletest-runner_ before running
it against the staging cluster (or production at your own risk). Coder provides
different
[workspace configurations](https://github.com/coder/coder/tree/main/scaletest/templates)
that operators can deploy depending on the traffic projections.

There are a few cluster options
[available](https://github.com/coder/coder/tree/main/scaletest/templates/scaletest-runner):
There are a few cluster options available:

| Workspace size | vCPU | Memory | Persisted storage | Details |
| -------------- | ---- | ------ | ----------------- | ----------------------------------------------------- |
Expand Down