Skip to content

Commit

Permalink
Updated ReadMe file as per review
Browse files Browse the repository at this point in the history
Signed-off-by: Nihal LK <[email protected]>
  • Loading branch information
Nihal LK committed Oct 9, 2024
1 parent 49410fc commit 4a9418d
Showing 1 changed file with 8 additions and 4 deletions.
12 changes: 8 additions & 4 deletions performance-test/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -101,20 +101,24 @@
https://mosip.atlassian.net/wiki/spaces/PT/pages/1227751491/Steps+to+set+up+the+local+system#PluginManager
### Designing the workload model for performance test execution

* Calculation of number of users depending on Transactions per second (TPS) provided by client

* The script and the below calculation is preconfigured as per 100 tps, if you are testing for other tps, the below values neds to be adjusted.

* Applying little's law
* Users = TPS * (SLA of transaction + think time + pacing)
* TPS --> Transaction per second.

* For the realistic approach we can keep (Think time + Pacing) = 1 second for API testing
* Calculating number of users for 10 TPS
* Users= 10 X (SLA of transaction + 1)
= 10 X (1 + 1)
= 20
* Users= 100 X (SLA of transaction + 1)
= 100 X (1 + 1)
= 200
### Usage of Constant Throughput timer to control Hits/sec from JMeter
* In order to control hits/ minute in JMeter, it is better to use Timer called Constant Throughput Timer.

* In order to control hits/ minute in JMeter, it is better to use Timer called Constant Throughput Timer. This is calculated explicitly for each thread group based on the scenario's weightage

* If we are performing load test with 10TPS as hits / sec in one thread group. Then we need to provide value hits / minute as in Constant Throughput Timer
* Value = 10 X 60
Expand Down

0 comments on commit 4a9418d

Please sign in to comment.