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.

Sign up for GitHub

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

Jump to bottom

docs: Document max-concurrent-tests #172

Merged
merged 1 commit into from
Jul 15, 2024
Merged

docs: Document max-concurrent-tests #172

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
10 changes: 10 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -90,3 +90,13 @@ helm upgrade -i k6-loadtester flagger-k6-webhook
--set webhook.vars.K6_CLOUD_TOKEN=token
--set webhook.vars.SLACK_TOKEN=slack_token
```
## Limited concurrent test runs
Whenever a k6 test is started, that process has to be managed by the application in order to avoid zombie processes.
This requires additional resources and the number of parallel test runs is therefore limited.
By default, that limit is set to 1,000 *parallel* k6 processes which can be configured using the `MAX_CONCURRENT_TESTS` environment variable or the `--max-concurrent-tests` flag.
If a new test request is received while the limit is reached, the request will be rejected with a HTTP 429 status.
zerok marked this conversation as resolved.
Show resolved Hide resolved
The response also includes a `Retry-After` header that should be respected by the client.
Loading