This feature makes it easier for the tester to understand the limits of the target servers or the load engines when loading a certain scenario - giving him more control.
With this feature, you can limit the RPS (Requests Per Second) of the load in order to avoid creating a bottleneck. For example: if you believe that 500 RPS will create a bottleneck on the app servers side, you can limit the RPS to 400. If it reaches 400 and everything goes smoothly, you can increase the RPS limit to 450.
This enables you to test load at the maximum capacity without crashing the servers. This is a best practice for the following scenarios:
1. Running a soak test.
2. Running multi instance tests with maximum threads per engine.
Setting RPS Limits 'On The Fly'
An Example of the Limit RPS Feature
In this example of a load report, the green line represents the Hits Per Second KPI.
In this scenario, we decreased the RPS Limit at 00:14 to 15. This enables you to view the outcome at this point in time.