Lexmark X925 Lexmark Document Distributor - Page 31

System sizing guidelines, Peak demand

Page 31 highlights

Installing Lexmark Document Distributor 31 With this type of setup, you need additional computers, as well as a hardware load balancer or GSS. You also need to manually configure these systems to be identical. Note: Printers that do not support eSF applications cannot be used with an LDD system that uses a hardware load balancer or GSS. System sizing guidelines There are two main factors for determining the number of servers required to process jobs efficiently: • Peak demand-This is usually the deciding factor when the average execution time for a solution is under 30 seconds. • Concurrency-This is usually the deciding factor when the average execution time for a solution is over 30 seconds. Additionally, the database, when installed on the recommended hardware and connected using Gigabit Ethernet, can process 200,000 logged messages per hour, which is approximately 40,000 jobs per hour when using a typical solution (five logged messages per job). If this limit is reached, then it may be necessary to use multiple LDD systems. Peak demand Use the following formulas to determine the number of servers necessary to handle peak loads for a particular solution: (System‑wide hourly job rate) = (system printer capacity) x (jobs per printer per day) / (length of business day) (Peak demand) = 2 x (system‑wide hourly job rate) (Minimum number of servers) = (peak demand) / (single‑server throughput for current solution) Consider the following example: • Each server in your system can process 3000 jobs per hour using the solution. • There is capacity for 300 printers in your system. • Each printer in your system averages 100 jobs per day. Perform the following calculations: 1 Determine the system‑wide hourly job rate: (300 printers) x (100 daily jobs/printer) / (8 hours/day) = 3750 jobs/hour 2 Determine the peak demand: 2 x (3750 jobs/hour) = 7500 jobs/hour 3 Determine the minimum number of servers: (7500 jobs/hour) / (3000 jobs/hour) = 2.5 Rounding up, the system should include three servers to reliably handle the peak load for a solution with average execution time below 30 seconds. The single‑server throughput for a solution must be determined by the solution developer, though the following typical throughputs on a server with the recommended hardware may help determine a rough estimate: Solution processing load Functions used Typical • Some image processing • Printing Average single‑server throughput 6000-8000 jobs per hour

  • 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

With this type of setup, you need additional computers, as well as a hardware load balancer or GSS. You also need to
manually configure these systems to be identical.
Note:
Printers that do not support eSF applications cannot be used with an LDD system that uses a hardware load
balancer or GSS.
System sizing guidelines
There are two main factors for determining the number of servers required to process jobs efficiently:
Peak demand
—This is usually the deciding factor when the average execution time for a solution is under 30
seconds.
Concurrency
—This is usually the deciding factor when the average execution time for a solution is over 30 seconds.
Additionally, the database, when installed on the recommended hardware and connected using Gigabit Ethernet, can
process 200,000 logged messages per hour, which is approximately 40,000 jobs per hour when using a typical solution
(five logged messages per job). If this limit is reached, then it may be necessary to use multiple LDD systems.
Peak demand
Use the following formulas to determine the number of servers necessary to handle peak loads for a particular solution:
(System
wide hourly job rate)
= (system printer capacity) x (jobs per printer per day) / (length of business day)
(Peak demand)
= 2 x (system
wide hourly job rate)
(Minimum number of servers)
= (peak demand) / (single
server throughput for current solution)
Consider the following example:
Each server in your system can process 3000 jobs per hour using the solution.
There is capacity for 300 printers in your system.
Each printer in your system averages 100 jobs per day.
Perform the following calculations:
1
Determine the system
wide hourly job rate:
(300 printers) x (100 daily jobs/printer) / (8 hours/day) =
3750 jobs/hour
2
Determine the peak demand:
2 x (3750 jobs/hour) =
7500 jobs/hour
3
Determine the minimum number of servers:
(7500 jobs/hour) / (3000 jobs/hour) =
2.5
Rounding up, the system should include three servers to reliably handle the peak load for a solution with average
execution time below 30 seconds.
The single
server throughput for a solution must be determined by the solution developer, though the following typical
throughputs on a server with the recommended hardware may help determine a rough estimate:
Solution processing load
Functions used
Average single
server throughput
Typical
Some image processing
Printing
6000–8000 jobs per hour
Installing Lexmark Document Distributor
31