Skip to content

Fix images and text on "Stress testing" guide #1056

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

Merged
merged 1 commit into from
Feb 21, 2023
Merged

Fix images and text on "Stress testing" guide #1056

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
9 changes: 7 additions & 2 deletions src/data/markdown/translated-guides/en/05 Test Types/03 Stress testing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,8 +93,9 @@ export default function () {
</CodeGroup>

The VU chart of a stress test should look similar to this:
5 minutes. We have also included a recovery stage at the end, where the system is gradually
decreasing the load to 0.")
![Virtual user chart of an API stress test](./images/stress-test.png)

This configuration increases the load by 100 users every 2 minutes and stays at this level for 5 minutes. We have also included a recovery stage at the end, where the system is gradually decreasing the load to 0.

If your infrastructure is configured to auto-scale, this test will help you to determine:

Expand Down Expand Up @@ -205,6 +206,10 @@ export default function () {

The VU chart of a spike test should look similar to this:

![Virtual user chart of a spike test](./images/spike-test.png)

Note, the test starts with a period of 1 minute of low load, a quick spike to very high load, followed by a recovery period of low load.

Remember that the point of this test is to suddenly overwhelm the system. Don't be afraid to increase the number of VUs beyond your worst-case prediction.
Depending on your needs, you may want to extend the recovery stage to 10 or more minutes to see when the system finally recovers.

Expand Down