HP ProLiant 4500 Compaq ProLiant Cluster HA/F100 and HA/F200 Administrator Gui - Page 114

Managing Cluster Performance, Managing the Compaq ProLiant Clusters HA/F100 and HA/F200

Get HP ProLiant 4500 PDF manuals and user guides View all HP ProLiant 4500 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 114 highlights

Managing the Compaq ProLiant Clusters HA/F100 and HA/F200 5-11 Managing Cluster Performance As applications or resources transfer from one server to another, the performance of the clustered servers will likely change. The extent of the change depends on how well equipped the other node is to handle the increased workload. This is especially obvious after a server failure, where all of the cluster resources may move to the other server. Use the Windows NT Performance Monitor to observe and track system performance. Some applications have their own internal performance measurement capabilities. Constant monitoring of each system's performance in a cluster may identify a disparity in the workload being performed by each server. Adjust the distribution of the cluster applications so that the overall cluster performance is maximized. Dynamic load balancing is not available in the initial release of MSCS. However, MSCS can manually load balance your cluster nodes. Information obtained from Performance Monitor can be used to determine whether either of the cluster nodes is operating at too high a performance level. Then use Cluster Administrator to fail over as many cluster groups as necessary to balance the load of each cluster node. Additionally, disk I/O may be balanced across the dual host bus adapters in a Compaq ProLiant Cluster HA/F200 configuration. This functionality is only available when accessing two separate RAID arrays. The timing of manual load balancing depends on the type of group to be moved and how many clients are using the group. File and print services are normally not business-critical, nor do they sustain an extremely high utilization rate. For these reasons, file and print services are good candidates to move whenever load balancing needs to occur, even when the overall cluster utilization is high. However, some applications, such as databases, should not be moved from one server to another during peak processing periods. To move a database from one server to another, the database must be shut down and restarted. Users do not have access to the database during the time it takes the database to restart. Move a database group to another server during nonpeak hours.

  • 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
Managing the Compaq ProLiant Clusters HA/F100 and HA/F200
5-11
Managing Cluster Performance
As applications or resources transfer from one server to another, the
performance of the clustered servers will likely change. The extent of the
change depends on how well equipped the other node is to handle the
increased workload. This is especially obvious after a server failure, where all
of the cluster resources may move to the other server.
Use the Windows NT Performance Monitor to observe and track system
performance. Some applications have their own internal performance
measurement capabilities. Constant monitoring of each system’s performance
in a cluster may identify a disparity in the workload being performed by each
server. Adjust the distribution of the cluster applications so that the overall
cluster performance is maximized.
Dynamic load balancing is not available in the initial release of MSCS.
However, MSCS can manually load balance your cluster nodes. Information
obtained from Performance Monitor can be used to determine whether either
of the cluster nodes is operating at too high a performance level. Then use
Cluster Administrator to fail over as many cluster groups as necessary to
balance the load of each cluster node. Additionally, disk I/O may be balanced
across the dual host bus adapters in a Compaq ProLiant Cluster HA/F200
configuration. This functionality is only available when accessing two separate
RAID arrays.
The timing of manual load balancing depends on the type of group to be
moved and how many clients are using the group. File and print services are
normally not business-critical, nor do they sustain an extremely high
utilization rate. For these reasons, file and print services are good candidates to
move whenever load balancing needs to occur, even when the overall cluster
utilization is high.
However, some applications, such as databases, should not be moved from one
server to another during peak processing periods. To move a database from
one server to another, the database must be shut down and restarted. Users do
not have access to the database during the time it takes the database to restart.
Move a database group to another server during nonpeak hours.