Lexicon
Explanation of the terms used in the interface
Performances
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 95P
The 95th percentile standard means the 95% of requests are faster than the indicated value.
You can compare 95th percentile response time and average response time. If the difference is significant, you could assume there is a worst case, and you may want to investigate.
