Hi Team,
Need some clarification
How did it calculated “Each iteration will be ~515ms” ?
Can you please help me to understand this?
Also are there any reference video/site to understand all type of executors with examples?
Thanks
Thanks for pointing at this, we are looking into it and will get back to you. I think the 515ms comes from assuming the request will take an average 15ms, and adding the sleep of 0.5s, the complete iteration will take around 515ms. However, I’m double-checking in case I missed something.
In terms of examples, you can find a bit more details in https://github.com/grafana/k6-learn/blob/main/Modules/III-k6-Intermediate/08-Setting-load-profiles-with-executors.md.
The topic has also been discussed in some episodes of k6 Office Hours:
- Load testing types and k6 executors (k6 Office Hours #67) - YouTube
- Using executors and stages in k6 with Théo Crevon (k6 Office Hours #40) - YouTube
- How to design a workload model in k6, with the k6 Developer Advocates (k6 Office Hours #42) - YouTube
Let me know if you still have doubts with the Office Hours content. We can always improve this part of the documentation. We are working on Restructure and rewrite Scenarios section · Issue #808 · grafana/k6-docs · GitHub, and can use the feedback for sure.
Cheers!
I can confirm this was the explanation for the 515ms. What we did is correct the text to avoid confusion: clarify comment in the example · grafana/k6-docs@0dd0f3a · GitHub and next time we release the docs it will be updated.
Again, many thanks for catching this, it helps improve the documentation 
Cheers!
Hi @eyeveebe
How did you calculated average 15ms ?
Can you please clarify.
Thanks
This was just probably a guess from the writer of the docs. Most probably he/she ran the example while writing the docs and saw that the average for that one run was 15ms in the output. The docs where confusing, so we rephrased that sentence, as the time to finish a request will vary.
Cheers!