How to understand test data requirements for load test?

Hi All,
I am pretty new to load testing and K6, been trying to get my heads around how to manage the test data required for POST API load testing.

How do we calculate the number of unique test data (e.g. login data – username/ password combinations) required for simulating a concurrent user load of 5000 users/ hour ? Also, what is the role of iterations in this context ?

This is with the assumption-

  • at any given point in time one VU will use a unique test data and no collisions happen
  • API under test needs unique data each time to return a success response

Hi @sumanta.r86,
welcome to the community forum! :tada:

You can check this guide in k6 documentation about Data parameterization where it explains how to use dynamic data from indexed data sources.

Let me know if it helps.

1 Like

Thanks. This was helpful.