Apdex (Application Performance Index) is an open standard for turning response times into a single satisfaction score between 0 and 1. You choose a target threshold T. Requests at or under T are satisfied, those between T and 4T are tolerating, and slower ones are frustrated.
Why it matters
A score is easy to put on a dashboard and to compare across services, which helps non-specialists see whether performance is acceptable. It reduces a mass of timing data to one number that can be tracked over time or alerted on.
Example
The formula is:
Apdex = (satisfied + tolerating / 2) / total samples
With T = 0.5 s and 100 requests: 80 under 0.5 s, 15 between 0.5 and 2 s, 5 slower.
Apdex = (80 + 15/2) / 100 = 0.875
A common reading is 0.94 to 1.0 excellent, 0.85 to 0.93 good, 0.70 to 0.84 fair, and lower is poor.
Common mistakes
- Choosing T carelessly. A loose T makes the score look great while users wait.
- Using the same T for very different operations, such as search and report export.
- Treating the number as precise. It hides the shape of the distribution, so check percentiles as well.
Related
Get notified when this term updates
Plus occasional practical tips on uptime and monitoring, nothing else. Unsubscribe anytime.
This page is general information written by our editorial team and updated when documentation changes. Servers and providers differ, so test changes safely first. See our editorial policy and disclaimer.