Lexicon
Explanation of the terms used in the interface
Performance
Impact
Impact tells where the time is spent. It depends on the response time and throughput compared to other requests.
By default everything is ordered by impact to show the requests that matter most in your application.
High impact requests are either very slow and/or very often executed compared to others. A small improvement on a high impact request may result in the biggest performance win.
Slow, low impact requests mean they aren’t often executed. You may have to optimize them if you think they are important in your app, or consider to improve or remove a feature.
Runtime
The runtime chart and the runtime column can show the average, the median (P50), P95, P99, or the slowest request (MAX). P95 is the default.
- AVG is the mean. A few slow requests pull it up.
- P50 is the median. Half of the requests are faster than this value.
- P95 means 95% of requests are faster. It shows slow requests that still happen often.
- P99 means 99% of requests are faster. It shows rare slow requests.
- MAX is the slowest request in the period.
Compare them. If P95 or P99 is much higher than the average or P50, a minority of requests is much slower than the rest, and it is worth investigating.
