background image
<< Resource Utilizations | Bandwidth consumed >>
<< Resource Utilizations | Bandwidth consumed >>

Processor Time and Queue

Exemplar for Technical Team Members

Figure 16.4 Processor Time and Queue
Additional Considerations
Points to consider when reporting resource utilizations include:
·
Know when to report all of the data and when to summarize. Very often, simply
reporting the peak value for a monitored resource during the course of a test is
adequate. Unless an issue is detected, the report only needs to demonstrate that the
correct metrics were collected to detect the issue if it were present during the test.
·
Overlay resource utilization metrics with other load and response data.
Resource utilization metrics are most powerful when presented on the same graph as
load and/or response time data. If there is a performance issue, this helps to identify
relationships across various metrics.
·
If you decide to present more than one data point, present them all. Resource
utilization rates will often change dramatically from one measurement to the next.
The pattern of change across measurements is at least as important as the current
value. Moving averages and trend lines obfuscate these patterns, which can lead to
incorrect assumptions and regrettable decisions.
Volumes, Capacities, and Rates
Volume, capacity, and rate metrics are also frequently requested by stakeholders, even
though the implications of these metrics are often more challenging to interpret. For this
reason, it is important to report these metrics in relation to specific performance criteria