Lexmark X792 Lexmark Document Distributor - Page 65

Tuning the load balancer for unequal servers, Assigning servers to only run LMC or process jobs

Get Lexmark X792 PDF manuals and user guides View all Lexmark X792 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 65 highlights

Monitoring and maintaining the system 65 Tuning the load balancer for unequal servers When all servers in the system are approximately equal, server loads should be optimal without manually tuning the load balancer. However, when servers are unequal, the least powerful machine determines the overall throughput unless you compensate by manually assigning a load balancing factor to each server. Since more powerful machines can run more concurrent jobs and complete each job in less time, routing more traffic to them increases the overall job capacity of the system. The LDD load balancer component is composed of three different Tomcat load balancing workers that separately manage Lexmark Management Console (LMC) sessions, job submissions from e‑Task 2 and e‑Task 3 printers, and job submissions from e‑Task printers. The adjustment shown here affects the e‑Task 2, e‑Task 3, and e‑Task load balancers, but not the LMC load balancer. Each load balancer distributes jobs to servers in proportion to the load balancing factors assigned to each server. For example, in a system with three servers with load balancing factors of 10,10, and 20, the first two servers each receive 25% of jobs, and the third receives 50%. The ideal job distribution depends on the hardware, network environment, and the solution being run. The optimal proportions for load balancing factors can be found by running performance tests on each server. However, some factors such as memory, number of processors, or CPU speed may suggest an initial value for the load balancing factor to add more system capacity. Note, however, that performance improvements are not linear functions of numerical improvements in hardware. Perform the following steps on each server after initial values are determined for load balancing factors: 1 From the System Health dashboard, select the address of the server from the list in the Server Health section. 2 Adjust the Load Factor slider to the desired load balancing factor for the server. Note: These settings are not saved during an upgrade. If you upgrade your LDD system, then you must repeat these steps. Assigning servers to only run LMC or process jobs When using more than one server in a system, you can assign some servers to only run LMC and other servers to only process jobs. When all servers are separated in this manner, it is usually adequate to assign only one server to run LMC. When using a configuration 1‑N, X‑N, or X‑Y‑N system with the recommended hardware, it is recommend to do the following: • Install the server component on the RAID 1 array where the operating system is installed on the load balancer computer, and configure it to only run LMC. • Configure servers installed on dedicated computers to only process jobs. 1 Launch JK Status Manager from your Web browser using the URL http://loadbalancer:9780/status/? opt=454, where loadbalancer is the computer where your load balancer is installed. Server information and the worker status for each of the three load balancing workers appear. Each server in the system is listed as a worker in each Balancer Members list. 2 For each server that should only process jobs, stop the associated worker on the adminloadbalancer load balancing worker, which balances requests to LMC: a In the "Worker Status for adminloadbalancer" section, click E beside the server name. b For Activation, select the Stopped option. c Click Update Worker.

  • 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
Tuning the load balancer for unequal servers
When all servers in the system are approximately equal, server loads should be optimal without manually tuning the
load balancer. However, when servers are unequal, the least powerful machine determines the overall throughput
unless you compensate by manually assigning a load balancing factor to each server. Since more powerful machines
can run more concurrent jobs and complete each job in less time, routing more traffic to them increases the overall
job capacity of the system.
The LDD load balancer component is composed of three different Tomcat load balancing workers that separately
manage Lexmark Management Console (LMC) sessions, job submissions from e
‑
Task 2 and e
‑
Task 3 printers, and job
submissions from e
‑
Task printers. The adjustment shown here affects the e
‑
Task 2, e
‑
Task 3, and e
‑
Task load balancers,
but not the LMC load balancer. Each load balancer distributes jobs to servers in proportion to the load balancing factors
assigned to each server. For example, in a system with three servers with load balancing factors of 10,10, and 20, the
first two servers each receive 25% of jobs, and the third receives 50%.
The ideal job distribution depends on the hardware, network environment, and the solution being run. The optimal
proportions for load balancing factors can be found by running performance tests on each server. However, some
factors such as memory, number of processors, or CPU speed may suggest an initial value for the load balancing factor
to add more system capacity. Note, however, that performance improvements are not linear functions of numerical
improvements in hardware.
Perform the following steps on each server after initial values are determined for load balancing factors:
1
From the System Health dashboard, select the address of the server from the list in the Server Health section.
2
Adjust the Load Factor slider to the desired load balancing factor for the server.
Note:
These settings are not saved during an upgrade. If you upgrade your LDD system, then you must repeat these
steps.
Assigning servers to only run LMC or process jobs
When using more than one server in a system, you can assign some servers to only run LMC and other servers to only
process jobs. When all servers are separated in this manner, it is usually adequate to assign only one server to run LMC.
When using a configuration 1
‑
N, X
‑
N, or X
‑
Y
‑
N system with the recommended hardware, it is recommend to do the
following:
•
Install the server component on the RAID 1 array where the operating system is installed on the load balancer
computer, and configure it to only run LMC.
•
Configure servers installed on dedicated computers to only process jobs.
1
Launch JK Status Manager from your Web browser using the URL
http://
loadbalancer
:9780/status/?
opt=454
, where
loadbalancer
is the computer where your load balancer is installed.
Server information and the worker status for each of the three load balancing workers appear. Each server in the
system is listed as a worker in each Balancer Members list.
2
For each server that should only process jobs, stop the associated worker on the adminloadbalancer load balancing
worker, which balances requests to LMC:
a
In the “Worker Status for adminloadbalancer” section, click
E
beside the server name.
b
For Activation, select the
Stopped
option.
c
Click
Update Worker
.
Monitoring and maintaining the system
65