Skip to content

Fix calculation for total requests in README #8

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

Open
mesar-m wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix calculation for total requests in README #8

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 README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -288,7 +288,7 @@ This setting uses the [`constant-arrival-rate` scenario](https://grafana.com/doc

Given that each iteration executes only one Pizza request, the test will run 20 requests per second. Mathematically speaking:
- 20 iterations per second x 1 request per iteration = 20 requests per second
- 20 requests per second x 20 second = 200 requests
- 20 requests per second x 10 second = 200 requests

Run the test. After completion, you can see the test request rate by looking at the `http_reqs` metric, which reports the number of http requests and the request rate. In our example, it is close to our goal of 20 requests per second.

Expand Down Expand Up @@ -1042,4 +1042,4 @@ Still, the [Quickpizza repository](https://github.com/grafana/quickpizza) includ
- Examples using local or public extensions
- One example using the `k6-operator` to distribute the test load among Kubernetes Pods
- Other integrations with Grafana and the Grafana o11y stack
- And more!
- And more!