Skip to content
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

Docs: replace k6 Cloud mention #9599

Merged
merged 4 commits into from
Jun 8, 2023
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
Next Next commit
Replace k6 Cloud mention
  • Loading branch information
ppcano committed Jun 1, 2023
commit 57a72a750297022a213275e478de2e37f640668b
6 changes: 2 additions & 4 deletions docs/sources/clients/k6/write-scenario.md
Original file line number Diff line number Diff line change
Expand Up @@ -55,14 +55,12 @@ These parameters can be adjusted in the load test:

* The way to run k6

k6 can be run locally, self-managed in a distributed way,
or it can be run highly-scalable within the k6 cloud.
k6 supports three [execution modes](https://k6.io/docs/get-started/running-k6/#execution-modes) to run a test: local, distributed, and cloud.
Whereas running your k6 load test from a single (local
or remote) machine is easy to set up and fine for smaller Loki clusters,
the single machine does not load test large Loki installations,
because it cannot create the data to saturate the write path.
Therefore, it makes sense to run
the tests in the [k6 Cloud](https://k6.io/cloud/).
For larger tests, consider [these optimizations](https://k6.io/docs/testing-guides/running-large-tests/), or run them in [Grafana Cloud k6](https://grafana.com/products/cloud/k6) or a Kubernetes cluster with [k6-operator](https://github.com/grafana/k6-operator).
ppcano marked this conversation as resolved.
Show resolved Hide resolved

## Metrics

Expand Down