Hey all!
I’m new to K6 and Load testing in general. I wanted to check in and see if I was setting my target correctly given K6’s documentation. The site has an average of 115k sessions at around 80s per session. I end up with 2,555 concurrent users for the month. That seems high and when I go to out peak day, peak hours, I end up with around 150 concurrent users. Would I then set my target at 150? Or would it be better to set it at the monthly number? Thoughts?
Thanks!
Hi and welcome to the forums!
That’s really up to you to decide. The amount of load you test with is the maximum amount of concurrent connections you’ll know for sure will (or won’t) be handled by your service.
Three things to consider;
during peak - do all users access the same resource? I’ll go out on a limb here and say that likely they are not. If not, what is a reasonable usage pattern for your users? That is likely what you should test.
what is your goal? How many concurrent users do you want to support for? Are you satisfied with your system under test being able to handle 150 concurrent users? If so, then it makes total sense to test that.
If you set it at the monthly total, that would mean that you’re testing whether your system under test can manage the monthly total concurrently, which in your case is more than 17 times your current peak.
I would recommend that you check out the API load testing guide in the docs for a good primer on load testing. And don’t hesitate to get in touch if you have additional questions or thoughts!
Best regards, good luck, and stay safe.
Simme