Actions

An action is part of a transaction and usually consists of one or more requests. When testing web applications, an action resembles a page view. More...Hide...

The data shown here reflects the time spent on the execution routine of an action. Therefore, the action's runtime includes the runtime of a request (an HTTP operation, for instance) and the time required to prepare, send, wait for, and receive the data. If JavaScript is activated, these times are part of the measurement as well. If you actively wait for elements to appear or if you add pauses, the resulting waiting times are also included.

The error count defines the number of errors detected during the validation of the page or errors that occured during loading, such as timeouts or connection resets. See the Request Section for further details on connection resets.

For each action the corresponding Apdex value is listed. The Apdex, short for Application Performance Index, is a measure to express the degree of user satisfaction with the performance of a certain operation (see Wikipedia or the Apdex Alliance for more information). The general format of an Apdex value is P [T] (for instance: 0.75 [2.5]). P is the degree of user satisfaction in percent, represented by a number between 0 and 1. T is the configurable threshold in seconds for the runtime of a certain operation above which the user is usually no longer satisfied with the performance. See below for the resulting ratings based on P and how they are color-coded:

  •  0.94...1.00 / Excellent
  •  0.85...0.93 / Good
  •  0.70...0.84 / Fair
  •  0.50...0.69 / Poor
  •  0.00...0.49 / Unacceptable

The Summary chart section comprises all data across actions to allow for a quick overview on action problems and performance. The tabs in this chart section contain single charts that refer to one action.

In the following, all chart sections below visualize this information:

  • Overview: moving average and individual actions
  • Averages: median, mean, and moving average only
  • Counts/s: number of finished actions per second

Please note that the charts display compressed information which means that any kind of information has been mapped to chart pixels. Such a pixel can stand for any time period, depending on the total test duration. Therefore, the information you see is taken from several events within that time period and signifies a certain value range, defined by the minimum and the maximum value measured.

If the upper border of a chart is highlighted, the chart display has been capped.

*) Numbers may be projected

All Actions

Overview
charts/actions/All Actions.webp
Count/s
charts/actions/All Actions_CountPerSecond.webp
Averages
charts/actions/All Actions_Average.webp
Action Name
Count Errors Runtime [ms] Runtime Percentiles [ms] Apdex
Total 1/s 1/min 1/h* Total % Mean Min. Max. Dev. P50 P95 P99 P99.9
Totals (1 entry) 11,344,820 6,302.7 378,161 22,689,640 8 0.00% 47 43 7,087 10 40 40 50 70 1.00 [1.0]
EchoLatency 11,344,820 6,302.7 378,160.7 22,689,640 8 0.00% 47 43 7,087 10 40 40 50 70 1.00 [1.0]

Individual Actions

EchoLatency

Overview
charts/actions/EchoLatency.webp
Count/s
charts/actions/EchoLatency_CountPerSecond.webp
Averages
charts/actions/EchoLatency_Average.webp