Compaq ProLiant CL380 Compaq ProLiant CL380 Software User Guide - Page 107

Managing Cluster Performance, You can use the Windows Performance Monitor or the Novell NetWare

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

Page 107 highlights

System Management 6-13 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 performance change depends on how well equipped the other server node is to handle the increase in workload. This is especially obvious after a server failure, where all of the cluster resources may move to the other server. You can use the Windows Performance Monitor or the Novell NetWare MONITOR.NLM to observe and track system performance. Some applications may also 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 MSCS, Cluster Service, or NCS. However, MSCS, Cluster Service and NCS do offer the ability to manually load balance your server nodes. Under Windows, you can use information obtained from Performance Monitor to determine whether either of the server nodes is operating at too high a performance level. Use Cluster Administrator to fail over as many cluster groups as necessary to balance the load of each server node. Similarly, under Novell NetWare, use MONITOR.NLM to determine whether either of the server nodes is operating at too high a performance level. The timing of manually moving a cluster group to balance the load should depend strongly on what type of group needs 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. When a database is moved from one server to another, the database must be shut down and restarted. During the time it takes the database to restart, users do not have access to the database. In these cases, move a database group to another server during non-peak 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
System Management
6-13
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
performance change depends on how well equipped the other server node is to
handle the increase in workload. This is especially obvious after a server
failure, where all of the cluster resources may move to the other server.
You can use the Windows Performance Monitor or the Novell NetWare
MONITOR.NLM
to observe and track system performance. Some applications
may also 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 MSCS, Cluster Service, or NCS.
However, MSCS, Cluster Service and NCS do offer the ability to manually
load balance your server nodes. Under Windows, you can use information
obtained from Performance Monitor to determine whether either of the server
nodes is operating at too high a performance level. Use Cluster Administrator
to fail over as many cluster groups as necessary to balance the load of each
server node. Similarly, under Novell NetWare, use
MONITOR.NLM
to
determine whether either of the server nodes is operating at too high a
performance level.
The timing of manually moving a cluster group to balance the load should
depend strongly on what type of group needs 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. When a database is moved
from one server to another, the database must be shut down and restarted.
During the time it takes the database to restart, users do not have access to the
database. In these cases, move a database group to another server during
non-peak hours.