HP Surestore Disk Array 12h System Administrator's Guide for HP-UX, MPE, and W - Page 49

Selecting a Time Period for Analysis, Checking the Working Set Metric

Page 49 highlights

HP-UX Using the ARM Command Line Utilities for HP-UX Analyzing Disk Array Performance Selecting a Time Period for Analysis When analyzing performance, you must define the time period over which the analysis will be performed. A starting time (stime) and ending time (etime) establish the analysis period. For the best results, select a time period when performance may be a concern. This will produce the most meaningful analysis and recommendations. For example, if the heaviest load on the disk array occurs between the hours of 8:00 AM and 5:00 PM, restrict the analysis to this time period. If you include periods of less activity, the analysis may yield different results and consequently different recommendations. This occurs because activity is averaged over the entire analysis period, and periods of less activity will offset the effects of busier periods. Typically, you should select a period of time that represents normal system operation. Avoid any unusual events such as a Rebuild or changes made to array capacity. If you select a time period that includes an event that may distort the analysis, the utility will alert you and will not provide any recommendations. You can also control the display interval using the int option. This allows you to control how much detail you get when displaying the metrics. The display interval is the number of 15-minute increments. Checking the Working Set Metric A key factor in monitoring and maintaining optimal performance of the disk array is the Working Set metric. To ensure that disk array performance is maintained, you should access the performance metrics regularly and check the Working Set value. The Working Set performance metric is derived from the Write Working Set parameter. It indicates the ratio of the Write Working Set size to the amount of RAID 0/1 space available. For a detailed explanation of the Write Working Set and its impact on performance, refer to the HP SureStore E Disk Array 12H User's and Service Manual. To maintain performance, the amount of RAID 0/1 space should equal or exceed the Write Working Set, resulting in a Working Set value less than or equal to 1. A Working Set value greater than 1 indicates that the Write Working Set is larger than the available RAID 0/1 space and the disk array is servicing writes from RAID 5 space. If the Working Set consistently exceeds 1, the amount of RAID 0 /1 space available should be increased to improve performance. This can be accomplished in several ways as described in the following section. If the Working Set is consistently much less than 1, some of the RAID 0/1 capacity can be allocated to a new LUN without impacting performance. The remaining RAID 0/1 space should be adequate to accommodate the Write Working Set. 49

  • 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
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279

Using the ARM Command Line Utilities for HP-UX
Analyzing Disk Array Performance
49
HP-UX
Selecting a Time Period for Analysis
When analyzing performance, you must define the time period over which the analysis will be performed. A
starting time (
stime
) and ending time (
etime
) establish the analysis period. For the best results, select a
time period when performance may be a concern. This will produce the most meaningful analysis and
recommendations.
For example, if the heaviest load on the disk array occurs between the hours of 8:00 AM and 5:00 PM,
restrict the analysis to this time period. If you include periods of less activity, the analysis may yield
different results and consequently different recommendations. This occurs because activity is averaged over
the entire analysis period, and periods of less activity will offset the effects of busier periods.
Typically, you should select a period of time that represents normal system operation. Avoid any unusual
events such as a Rebuild or changes made to array capacity. If you select a time period that includes an
event that may distort the analysis, the utility will alert you and will not provide any recommendations.
You can also control the display interval using the
int
option. This allows you to control how much detail
you get when displaying the metrics. The display interval is the number of 15-minute increments.
Checking the Working Set Metric
A key factor in monitoring and maintaining optimal performance of the disk array is the Working Set
metric. To ensure that disk array performance is maintained, you should access the performance metrics
regularly and check the Working Set value.
The Working Set performance metric is derived from the Write Working Set parameter. It indicates the
ratio of the Write Working Set size to the amount of RAID 0/1 space available. For a detailed explanation
of the Write Working Set and its impact on performance, refer to the
HP SureStore E Disk Array 12H
User’s and Service Manual.
To maintain performance, the amount of RAID 0/1 space should equal or exceed the Write Working Set,
resulting in a Working Set value less than or equal to 1. A Working Set value greater than 1 indicates that
the Write Working Set is larger than the available RAID 0/1 space and the disk array is servicing writes
from RAID 5 space.
If the Working Set consistently exceeds 1, the amount of RAID 0 /1 space available should be increased to
improve performance. This can be accomplished in several ways as described in the following section.
If the Working Set is consistently much less than 1, some of the RAID 0/1 capacity can be allocated to a
new LUN without impacting performance. The remaining RAID 0/1 space should be adequate to
accommodate the Write Working Set.