Apdex is an industry-standard method for reporting and comparing application performance in terms of end user experience. Apdex uses a simple formula to calculate user satisfaction. The result is a single number - the Apdex ‘score’. APM presents this as a percentage.
The Apdex score is calculated using the following:
t - the ‘satisfied threshold’ (in seconds) under which the user is satisfied with an application’s response. By default, this is four seconds.
Satisfied count - the number of page load samples where the response time is less than the ‘satisfied threshold’ (t).
Tolerating count - the number of page load samples where the response time is between the ‘satisfied threshold’ (t) and the ‘tolerating threshold’ (by default, 4 x t).
Total samples - the total number of page load samples.
In APM, the samples used for an Apdex calculation are from the previous two hours.
The Apdex formula is as follows:
Apdext = (Satisfied count + (Tolerating count / 2)) / Total samples
So the Apdex score is simply a ratio of satisfied and tolerated page load response times to the total number of page load requests made. Each satisfied page load is counted as 1. Each tolerating page load is counted as 1/2. All others (those taking longer than the ‘tolerating threshold’ and those that fail) are counted as 0.
Within the Experience module in APM, each milestone in a script represents a distinct page load. So, each time a script runs, each milestone represents a sample in the Apdex calculation. An Apdex score of 1 (represented as 100% in APM) means that all milestones had page load times of less than t seconds. In other words, users would be 100% satisfied with the response times.
Apdex scores are calculated for every milestone, web path, and web application.
Milestone Apdex - is calculated based on the executions of a given milestone over the previous two hours.
Web path Apdex - is calculated based on the executions of all milestones on a given web path over the previous two hours.
Web application Apdex - is calculated based on the executions of all milestones, on all web paths, for a given web application over the previous two hours.
Modifying the Apdex thresholds
The thresholds you use depend on what response times you believe will satisfy your users and what they will tolerate. The Apdex number generated is a measure of how well you are meeting those expectations. By default, the ‘satisfied threshold’ is 4 seconds and the ‘tolerating threshold’ is 16 seconds. The Apdex score assumes this 1:4 ratio. Keep this in mind if you customize your thresholds.
To modify the Apdex thresholds:
- Log in to APM.
- Make sure you are using the correct organization
- Navigate to Experience > Web App Groups.
- Click Configure for the web app group containing the workflow you want to edit.
- In the Workflows… pane, click the edit icon next to the workflow you want to edit.
- In the Apdex Thresholds section, click the text: “The user is satisfied when …”.
- The Configure Apdex Thresholds dialog appears.
- If you want all milestones to have the same thresholds:
- Select All Milestones.
- Specify the Satisfied and Tolerating thresholds.
- If you want each milestone to have different thresholds:
- Select Per Milestone.
- Specify the Satisfied and Tolerating thresholds for each milestone.
- Click Submit.
- Click OK.
- Click Save.