<p>May I suggest taking a look at JMeter (<a href="https://jmeter.apache.org" rel="nofollow noreferrer">https://jmeter.apache.org</a>).
It's pretty much the OO standard for performance/load testing and comes with a lot of predefined report/KPI output types (<a href="https://jmeter.apache.org/usermanual/generating-dashboard.html" rel="nofollow noreferrer">https://jmeter.apache.org/usermanual/generating-dashboard.html</a>). We use it extensively as part of our deployment chain for post build/deploy reporting on test environments. During maximum load testing we stream JMeter performance metrics into InfluxDB and visualise them realtime using Grafana <a href="https://grafana.com/grafana/dashboards/13644" rel="nofollow noreferrer">https://grafana.com/grafana/dashboards/13644</a>.</p>

CC BY-SA 4.0
2021-10-13T21:53:14.483Z
2021-10-13T21:53:14.483Z
wowbagger
<p>I want to establish the benchmark behavior of my API through performance testing.<br />
The purpose is to ensure that the product meet or exceed requirements such as:</p>
<ul>
<li>Throughput</li>
<li>Response time</li>
<li>Stability</li>
<li>Resource usage</li>
</ul>
<p>Some of KPIs I'm aware of:</p>
<ul>
<li>Average response time</li>
<li>Max connexion number</li>
<li>Success rate</li>
</ul>
<p>Is there a number of other industry-defined KPIs and what are the most important metrics to consider when stress testing an API ?</p>

CC BY-SA 4.0
2023-03-08T21:24:15.783Z
You should read up on non-functional tests. Load testing, performance testing and stress test are some examples of this. They are not however interchangeable. You need to decide if you need to know the breaking point. For example, if you are offering a tax system, you need to account for a big part of the adult population to access the system when the annual tax season comes around. Realistic guesstimates are important. And keep in mind that x simultaneous requests is not equal to x concurrent users. If you need to support 600 concurrent users, it may be ok to have a max capof 400 reqs
JoSSte
<testing><metrics><kpi>
What are the metrics to consider when doing API performance testing?
storm
# What are the metrics to consider when doing API performance testing?

(Asked by: username_0 on 2021-08-19)

I want to establish the benchmark behavior of my API through performance testing.  
The purpose is to ensure that the product meet or exceed requirements such as:

* Throughput
* Response time
* Stability
* Resource usage

Some of KPIs I'm aware of:

* Average response time
* Max connexion number
* Success rate

Is there a number of other industry-defined KPIs and what are the most important metrics to consider when stress testing an API ?

**Tags:** testing, metrics, kpi

> **Comments:**
> **username_1**: You should read up on non-functional tests. Load testing, performance testing and stress test are some examples of this. They are not however interchangeable. You need to decide if you need to know the breaking point. For example, if you are offering a tax system, you need to account for a big part of the adult population to access the system when the annual tax season comes around. Realistic guesstimates are important. And keep in mind that x simultaneous requests is not equal to x concurrent users. If you need to support 600 concurrent users, it may be ok to have a max capof 400 reqs  

---

## 1 answers

### Answer by username_2 on 2021-10-13. Score: 0

May I suggest taking a look at JMeter (<https://jmeter.apache.org>).
It's pretty much the OO standard for performance/load testing and comes with a lot of predefined report/KPI output types (<https://jmeter.apache.org/usermanual/generating-dashboard.html>). We use it extensively as part of our deployment chain for post build/deploy reporting on test environments. During maximum load testing we stream JMeter performance metrics into InfluxDB and visualise them realtime using Grafana <https://grafana.com/grafana/dashboards/13644>.


---

