Average memory usage per execution
Introduced in V6.3 and previously restricted to objects of type Executable and Binary, this aggregate has now been extended to support the following objects:
|Average memory usage per execution||Activity||Aggregate|
|Indicates the average memory usage of all underlying executions before aggregation. The value is the average
memory usage of all executions (calculated with a 5-minute resolution) multiplied by their cardinalities and divided by the total cardinality.
High CPU usage changes
A new device warning event called High overall CPU usage has been introduced to better represent situations of high CPU consumption. This event is triggered when 70% of all logical processors are used, or in other words when at least 70% of the total CPU capacity of the device is consumed. This value is configurable.
The aggregate High device overall CPU time ratio represents the ratio of time where the device suffers from high overall CPU usage.
|High device overall CPU time ratio||Warnings||Aggregate|
|Indicates the ratio between the time that the device is in high overall CPU usage and its uptime.|
Deprecated fields and aggregates
To simplify high CPU events following the introduction of the new High overall CPU usage event, the following events and aggregates have been deprecated:
- The event High CPU usage has been renamed to High thread CPU usage and has been deprecated.
- The aggregate High CPU time has been renamed to High device thread CPU time ratio and has been deprecated.
Please note that CPU warning events in the user and device views still refer to High thread CPU usage and have not yet been ported to High overall CPU usage)
High application thread CPU time ratio
This new aggregate can be used to identify applications generating a large volume of High thread CPU usage events, or in other words applications with high CPU usage peaks. This aggregate is available for the following objects:
|High application thread CPU time ratio||Warnings||Aggregate|
|Indicates the ratio between the time that the underlying executions are in high thread CPU usage and their execution duration.|