Hi guys. We continue testing our platform and identifying bottlenecks in our system, but here is one thing that breaks our monitoring and comparing.
I’m sharing with you with 4 latest test run:
The 1st run
/k6/runs/657058 - ABORTED (BY SYSTEM)
- It should have to run 300 VUs for 10 minutes but dropped to 150 after 2 minutes of stage 2 running and then was going like this yet 3 minutes until aborted by system.
it says that the system under test is overloaded, and resulting in higher response times .
but on the graph it’s flatlined…
The 2nd run
/k6/runs/657167 – passed full scenario (25 min)
Seeing the first run we thought that maybe the reason of the strage 2 failing is our 3rd-party endpoints that have fallen 12K times and we commented them out having left 1 failing endpoint only. Ok, now it passes and gives us a chance to analyze the results.
The 3rd run
/k6/runs/657220 – aborted by limit
Your test is creating too many requests and metrics.
This is an anti-pattern when load testing, where you want many data points per URL and then look for trends in the data.
This issue is usually a result of query parameters that vary per request (tokens, resource or session IDs etc).
If you want to group multiple HTTP requests, we suggest you use the URL grouping feature of k6 to aggregate data into a single URL metric.
P.S don’t understand why this error appeared and interrupted the test session even though we have only several groups (total 5) wherein only 1 group contains endpoints where set a parametrization for some arguments in URL
The 4th run
/k6/runs/657258 – passed successfully again
P.S we decided to uncomment failing endpoints and run again with all endpoints and we wondered again, everything is passed again.
Please, could you help us to sort it out? Thanks