# TPS old ui

## What is TPS?

Usually **T**ransaction **P**er **S**econd (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:

&#x20;$$TPS = Virtual User / (response time + think time )$$

![Jmeter - Transaction Per Second](/files/-Ma7i_Glq2m69r0PWSjc)

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](/files/-Ma7j5GVyg7757rzGaHE)

## **How to Use TPS**

In this example we will use jmeter

Create -> JMeter Test -> Limit TPS

<figure><img src="/files/TScoinQdgajJrnkoNCq7" alt=""><figcaption></figcaption></figure>

We enter that value as much as we want to limit TPS.

![](/files/-Ma7kyIEP9Somop4_8hI)

We run the test.

You can see the hit values in the "Hits & Errors" graph in the Overview in the test report.

![](/files/-Ma7lB9273JrHzb8q65U)

At the same time, we can see that the "Avg. Throughput / RPS" value in the "Summary Report" tab is limited to 10.

![](/files/-Ma7lXn67Jmwp9jxnUmM)

If we run the same test without TPS limit, we can see that the "Avg. Throughput / RPS" value is quite high, as seen below.

![](/files/-Ma7lpVsBeiNYwrWifrE)

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!

{% content-ref url="/pages/-MUSAunBwe2J09CIl1hu" %}
[JMeter Test](/create-test/jmeter-test.md)
{% endcontent-ref %}

If you don't see the answer to your question here, please [reach out to us](https://loadium.com/contact-us/) to let us know! We're always improving our documentation.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://wiki.loadium.com/test-settings/what-is-tps.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
