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

Fix small typo in api-load-testing.md #1865

Merged
merged 1 commit into from
Feb 13, 2025
Merged

Fix small typo in api-load-testing.md #1865

Show file tree
Hide file tree
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
4 changes: 2 additions & 2 deletions docs/sources/k6/next/testing-guides/api-load-testing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -148,7 +148,7 @@ To reach a request-rate target (`RequestsRate`), follow this approach:

1. Set the rate frequency to the time unit of the target. Per second or per minute.
1. Get the number of requests per iteration (`RequestsPerIteration`).
1. Set the iteration rate to the requests per second target divided by the number of requests per iteration.
1. Set the iteration rate to the requests per second target divided by the number of requests per iteration.
`rate` = `RequestsRate ÷ RequestsPerIteration`.

To reach target of 50 reqs/s with the previous example:
Expand Down Expand Up @@ -296,7 +296,7 @@ A load test can run thousands or millions of script iterations, each with dozens
Every test should have a goal.
Engineering organizations set their reliability goals using [Service Level Objectives](https://en.wikipedia.org/wiki/Service-level_objective) (SLOs) to validate availability, performance, or any performance requirements.

SLOs maybe defined at distinct scopes, such as on the level of an infrastructure component, of an API, or of the entire application.
SLOs may be defined at distinct scopes, such as on the level of an infrastructure component, of an API, or of the entire application.
Some example SLOs could be:

- That 99% of APIs returning product information respond in less than 600ms.
Expand Down
2 changes: 1 addition & 1 deletion docs/sources/k6/v0.56.x/testing-guides/api-load-testing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -296,7 +296,7 @@ A load test can run thousands or millions of script iterations, each with dozens
Every test should have a goal.
Engineering organizations set their reliability goals using [Service Level Objectives](https://en.wikipedia.org/wiki/Service-level_objective) (SLOs) to validate availability, performance, or any performance requirements.

SLOs maybe defined at distinct scopes, such as on the level of an infrastructure component, of an API, or of the entire application.
SLOs may be defined at distinct scopes, such as on the level of an infrastructure component, of an API, or of the entire application.
Some example SLOs could be:

- That 99% of APIs returning product information respond in less than 600ms.
Expand Down