Powered By GitBook
TPS
What is , How to Use & Things to Pay Attention

What is TPS?

Usually Transaction Per Second (TPS), which plays an important role in load testing, shows the number of processes completed in one second. In other words, it can be calculated based on how many transactions are executed over a certain duration of the test and then calculate it for a second.
TPS (Transaction per Second) and response times are related. The following relationship is between TPS, concurrent virtual users and response time:
TPS=VirtualUser/(responsetime+thinktime)TPS = Virtual User / (response time + think time )
​
Jmeter - Transaction Per Second
The graph below shows the average response time as 800ms.
If we calculate TPS, 5 / 0.8sec = 6.25 TPS (VirtualUser / Response Time = TPS)
Jmeter Aggregate Report

How to Use it

In this example we will use jmeter
New Test -> JMeter Test -> Limit TPS
We enter that value as much as we want to limit TPS.
We run the test.
You can see the hit values in the "Hits & Errors" graph in the Overview in the test report.
At the same time, we can see that the "Avg. Throughput / RPS" value in the "Summary Report" tab is limited to 10.
If we run the same test without TPS limit, we can see that the "Avg. Throughput / RPS" value is quite high, as seen below.
In summary, TPS in the performance test cannot be used as a performance metric alone. Transaction on execution time can be analyzed by comparing TPS with average transaction response time.
Happy testing!
If you don't see the answer to your question here, please reach out to us to let us know! We're always improving our documentation.
Last modified 4mo ago
Copy link