Bandwidth consumed
or a specific performance issue. Some examples of commonly requested volume,
capacity, and rate metrics include:
·
Bandwidth consumed
·
Throughput
·
Transactions per second
·
Hits per second
·
Number of supported registered users
·
Number of records/items able to be stored in the database
Exemplar
Figure 16.5 Throughput
Additional Considerations
Points to consider when reporting volumes, capacities and rates include:
·
Report metrics in context. Volume, capacity, and rate metrics typically have little
stand-alone value.
·
Have test conditions and supporting data available. While this is a good idea in
general, it is particularly important with volume, capacity, and rate metrics.
·
Include narrative summaries with implications. Again, while this is a good idea in
general, it is virtually critical to ensure understanding of volume, capacity, and rate
metrics.
Component Response Times
Even though component response times are not reported to stakeholders as commonly as
end-user response times or resource utilization metrics, they are frequently collected and
shared with the technical team. These response times help developers, architects,
database administrators (DBAs), and administrators determine what sub-part or parts of
the system are responsible for the majority of end-user response times.
