Over a million developers have joined DZone.

Percentiles Made Easy

· Performance Zone

Evolve your approach to Application Performance Monitoring by adopting five best practices that are outlined and explored in this e-book, brought to you in partnership with BMC.

Performance monitoring comes in all different shapes and sizes, but the end goal is the same. Performance monitoring tools exist to help ensure a fast and stable quality of service. Statistically speaking, there are many methods to determine just how good of an overall experience your application is providing, but today we are going to focus on percentiles. I’ll explain what percentiles are and how they should be used to understand your application performance better.

When you want to know how your application is performing from a macro perspective, you need to understand the concept of percentiles. Let’s take a look at an example. Figure 1 below is a histogram that represents transaction response times (you can click on the chart to see a larger version in a new tab). Each bar represents a grouping of transactions that fall within 400 ms of each other, with the fastest group on the left.

μ(a) from our histogram is the arithmetic mean or average response time. You’ll also notice a vertical dotted line labeled "95". This line represents the associated percentile. For example, the 95th percentile (shown) is roughly 15 seconds. This means that 95% of the transactions completed in 15 seconds or less. Ideally we want as many of our transactions as possible to have the fastest response time possible, so in an ideal world the 95th percentile line would shift left to approach μ(a). Percentiles, when compared with averages, tell us how consistent our application response times are. Let’s take a look at percentiles and averages plotted on the same chart.

Figure 2 above shows the average response time (ART) in green and the 95th percentile plotted in blue. You can see that the ART peaks out at about 1400 ms, while the 95th percentile tops out at about 2600 ms. What does this tell us and what should our response be? Well, it depends on how fast you want your application to run.

  • If having a lot of transactions that take between 1.4 and 2.6 seconds is OK for your particular application, then you are probably in good shape and don’t have much to do except for tracking down the outliers (the 5% of transactions that take longer than 2600 ms) and figuring out if you can make them faster.
  • If you need the majority of your transactions to complete in less than 1400 ms, then know you have a lot of work to do with optimizing your platform since so many transactions take longer than 1400 ms.

The whole point of this discussion is to provide an introduction to percentiles and to let you know how to interpret and react to the data once you have it plotted out. Percentiles are just another statistical tool that is available to help manage application performance and, like any tool, you need to know how to use it for it to be valuable. If you’re looking to make your application faster and more stable, you can try AppDynamics Pro for free today by clicking here.

Learn tips and best practices for optimizing your capacity management strategy with the Market Guide for Capacity Management, brought to you in partnership with BMC.


Published at DZone with permission of Jim Hirschauer, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}