Performance Monitor allows you to track a storage array’s
key performance data and identify performance bottlenecks in your
system. You can use Performance Monitor to perform these tasks:
View in real time the values of the data collected for a monitored
device. This capability helps you to determine if the device is experiencing
any problems.
Identify when a
problem started or what caused a problem by seeing a historical view of a monitored device.
Specify the performance metric and the objects that you want to
monitor.
View data in tabular format (actual values of the collected metrics)
or graphical format (as line graphs), or export the data to a file.
Three types of performance monitoring exist:
Real-time graphical—Plots performance data on a graph
in near real time.
Real-time textual—Shows performance data in a table in
near real time.
Background (historical)—Plots graphical performance data
over a longer period. You can view background performance
data for a session that is currently in progress or for a session
that you previously saved.
This table shows some specific characteristics of each
type of performance monitoring:
Table 1. Characteristics of different types of performance monitoringFor real-time graphical performance monitoring has sampling interval of 5 seconds and the length of time displayed is 5 minutes rolling window. The maximum number of objects real-time graphical performance monitorings can display is five and has no ability to save data. Real-time graphical performance monitoring starts automatically when AMW opens and stops automatically when AMW closes. For real-time textual performance monitoring has sampling interval of 5—3600 seconds and the length of time displayed is the most current value. There is no limit in the maximum number of objects real-time textual performance monitorings can display and can save data. Real-time textual performance monitoring starts and stops manually. This performance monitoring also stops when the View Real-time Textual Performance Monitor dialog closes or the AMW closes. For background performance monitoring has sampling interval of 10 minutes and the length of time displayed is 7 days rolling window. The maximum number of objects real-time graphical performance monitorings can display is five and can save data. Background performance monitoring starts and stops manually. This performance monitoring also stops when the EMW closes or the firmware download starts.
Type of Performance Monitoring
Sampling Interval
Length of Time Displayed
Maximum Number of Objects Displayed
Ability to Save Data
How Monitoring Starts and Stops
Real-time
graphical
5 sec
5 min rolling
window
5
No
Starts automatically
when AMW opens. Stops automatically when AMW closes.
Real-time
textual
5-3600 sec
Most current
value
No limit
Yes
Starts and
stops manually. Also stops when View Real-time Textual Performance
Monitor dialog closes or AMW closes.
Background
10 min
7 day rolling
window
5
Yes
Starts and
stops manually. Also stops when EMW closes or firmware download starts.
Keep these guidelines in mind when using Performance Monitor:
Each time the sampling interval elapses, the Performance Monitor
queries the storage array again and updates the data. The impact to
storage array performance is minimal.
The background monitoring process samples and stores data for
a seven-day time period. If a monitored object changes during this
time, the object does not have a complete set of data points spanning
the full seven days. For example, virtual disk sets can change as
virtualDisks are created, deleted, mapped, or unmapped or physical
disks can be added, removed, or failed.
Performance data is collected and displayed only for an I/O host
visible (mapped) virtual disk, a snapshot group repository virtual
disk, and a consistency group repository virtual disk. Data for a replication repository
virtual disk is not collected.
The values reported for a RAID controller module or storage array
might be greater than the sum of the values reported for all the
virtual disks. The values reported for a RAID controller module or
storage array include both host I/Os and I/Os internal to the storage
array (metadata reads and writes), whereas the values reported for
a virtual disk include only host I/O.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\