HP 3PAR StoreServ 7400 2-node HP 3PAR System Reporter 3.1.0 Software User& - Page 110

VV Cache Performance Reports, Table 48 Performance Metrics for PD, Port

Page 110 highlights

Table 48 Performance Metrics for PD, Port, LD and VLUN Performance Reports (continued) Metric Total Svct ms Read IOSz KBytes Write IOSz KBytes Total IOSz KBytes Queue Length Description Average total (read + write) service time in millisec. Average size of read operations in KBytes. Average size of write operations in KBytes. Average size of read and write operations in KBytes. Queue length at the sample time. Note that (unlike the other metrics above), the queue length is an instantaneous measure at the sample time, not an average over the sample interval. Please note that due to the way that RCFC ports process data, the Queue Length may not be a valid measure. Avg Busy % The percentage of time that the object is busy (i.e., has at least one outstanding IO operation). Note that this is not the same thing as the percentage of available object bandwidth that is being used. For example, a port shown as 50% busy may have much less than 50% of its bandwidth utilized. This is because the port may be idle for a substantial period of time between the request and response. Please note that for RCFC ports, the value will always be at 100% since the read requests are always waiting in the queue to be processed. For Histogram At Time and Histogram Versus Time report types, the PD, Port, LD and VLUN Performance reports show the read counts, write counts or total counts in various service time buckets. Depending on the Count control (see "Count" (page 85)), these counts are either the accesses within the sample interval or the total count from the beginning (object creation or system reboot) until the current sample. The CPU and VV Cache performance reports provide different metrics that are described separately in the following sections. VV Cache Performance Reports Table 49 (page 110) describes the metrics that are shown for VV Cache Performance Reports. Table 49 VV Cache Performance Report Metrics Metric Read Hits Read Misses Read Total Write Hits Write Misses Write Total Read Hit% Write Hit% Total Description Number of reads that hit in the cache. Number of reads that miss in the cache. Total number of reads. Not shown in charts. Number of writes for which the page is already in cache AND is dirty (i.e., has previously written data that has not yet been flushed to disk). Number of writes that miss in the cache. A write is considered a miss if the page is not in the cache or if the page is not dirty in the cache (see above). Total number of writes. Not shown in charts. Percentage of reads (out of total reads) that hit in the cache. Percentage of write (out of total writes) that hit in the cache. Total number of accesses (reads + writes). Not shown in charts. Node Cache Performance Reports Table 50 (page 111) describes the metrics that are shown for Node Cache Performance Reports. 110 Interpreting Report Metrics

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231

Table 48 Performance Metrics for PD, Port, LD and VLUN Performance Reports
(continued)
Description
Metric
Average total (read + write) service time in millisec.
Total Svct ms
Average size of read operations in KBytes.
Read IOSz KBytes
Average size of write operations in KBytes.
Write IOSz KBytes
Average size of read and write operations in KBytes.
Total IOSz KBytes
Queue length at the sample time.
Queue Length
Note that (unlike the other metrics above), the queue length is an instantaneous measure
at the sample time, not an average over the sample interval.
Please note that due to the way that RCFC ports process data, the Queue Length may
not be a valid measure.
The percentage of time that the object is busy (i.e., has at least one outstanding IO
operation).
Avg Busy %
Note that this is not the same thing as the percentage of available object bandwidth
that is being used. For example, a port shown as 50% busy may have much less than
50% of its bandwidth utilized. This is because the port may be idle for a substantial
period of time between the request and response.
Please note that for RCFC ports, the value will always be at 100% since the read
requests are always waiting in the queue to be processed.
For
Histogram At Time
and
Histogram Versus Time
report types, the PD, Port, LD and VLUN
Performance reports show the read counts, write counts or total counts in various service time
buckets. Depending on the
Count
control (see
“Count” (page 85)
), these counts are either the
accesses within the sample interval or the total count from the beginning (object creation or system
reboot) until the current sample.
The CPU and VV Cache performance reports provide different metrics that are described separately
in the following sections.
VV Cache Performance Reports
Table 49 (page 110)
describes the metrics that are shown for VV Cache Performance Reports.
Table 49 VV Cache Performance Report Metrics
Description
Metric
Number of reads that hit in the cache.
Read Hits
Number of reads that miss in the cache.
Read Misses
Total number of reads. Not shown in charts.
Read Total
Number of writes for which the page is already in cache AND is dirty (i.e., has previously written
data that has not yet been flushed to disk).
Write Hits
Number of writes that miss in the cache. A write is considered a miss if the page is not in the
cache or if the page is not dirty in the cache (see above).
Write Misses
Total number of writes. Not shown in charts.
Write Total
Percentage of reads (out of total reads) that hit in the cache.
Read Hit%
Percentage of write (out of total writes) that hit in the cache.
Write Hit%
Total number of accesses (reads + writes). Not shown in charts.
Total
Node Cache Performance Reports
Table 50 (page 111)
describes the metrics that are shown for Node Cache Performance Reports.
110
Interpreting Report Metrics