Skip to content

Commit 36d9da6

Browse files
author
Ivan Mirić
authored
Fix images and text on "Stress testing" guide (#1056)
Some of the images on the "Stress testing" guide[1] were removed and some text was mangled in #978. [1]: https://k6.io/docs/test-types/stress-testing/
1 parent 996c369 commit 36d9da6

File tree

1 file changed

+7
-2
lines changed

1 file changed

+7
-2
lines changed

src/data/markdown/translated-guides/en/05 Test Types/03 Stress testing.md

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -93,8 +93,9 @@ export default function () {
9393
</CodeGroup>
9494

9595
The VU chart of a stress test should look similar to this:
96-
5 minutes. We have also included a recovery stage at the end, where the system is gradually
97-
decreasing the load to 0.")
96+
![Virtual user chart of an API stress test](./images/stress-test.png)
97+
98+
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.
9899

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

@@ -205,6 +206,10 @@ export default function () {
205206

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

209+
![Virtual user chart of a spike test](./images/spike-test.png)
210+
211+
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.
212+
208213
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.
209214
Depending on your needs, you may want to extend the recovery stage to 10 or more minutes to see when the system finally recovers.
210215

0 commit comments

Comments
 (0)