Active users vs Requests Per Second

Gatling (Open-Source)
1

Hi,
I’m new to galing(and load testing). From the charts, My question is particularly regarding the Requests Per Sec. I’m having a hard time understanding what exactly does it mean, like what factors affect this metric.
I have the following setup and assmue that each user executes for a duration of 1 minute. Assume that the request is a http GET call, which ideally takes ~250ms

setUp(getCasesScenario
.inject(
incrementConcurrentUsers(250)
.times(5)
.eachLevelLasting(2 minutes)
.separatedByRampsLasting(1 minute)
)

Provided my active users vs rps report, the throughput at any point(even though the active users are >1000 ) is maintained ~100RPS. How exactly are these correlated?
Also, when I change one request per user(instead of 1-minute duration) the throughput of ~40RPS is constantly maintained.
Is there a way we can configure to maintain the proportion between active users and RPS at any given point
. I’m using gatling 3.1.
Any help would be highly appreciated

Capture.PNG
Capture.PNG935×376 30.3 KB

2

Hello Yashwanth
Generally, the RPS is the number of requests sent to the server at that particular second
It gets affected based on many factors:

  • number of users running in the scenario
  • the pause(think time) time between the requests, if added
  • based on server capacity, if it gets maxed out, the response time will increase and this is reduce the RPS
  • based on our machine capacity, it should be monitored as well for its capability to generate the requests as needed
    and there will be much more

not sure what happened on your side, but you can control the RPS in Gatling with throttling, check this out → https://gatling.io/docs/current/general/simulation_setup/#throttling

run a test once more by adding throttling, let’s see what happens