9.2

SizeRequest
8MB1
1MB2
2MB3
• Random Load Balancer: Each rendering request is sent to a random server.
• Round-robin Load Balancer: Requests are sent to servers in a set order. For example, if
you have three QuarkXPress Server instances and QuarkXPress Server Manager receives
ten rendering requests, the requests are distributed as follows:
QuarkXPress Server instance usedRequest
11
22
33
14
25
36
17
The first request is assigned to server #1, and the second request is assigned to server #2.
When the third request arrives, QuarkXPress Server Manager checks the loads that the two
servers are already handling and assigns the task to the server with the smallest load — in
this case, server #2.
If a request fails because a server stops responding or because of a "File Not Found" error,
QuarkXPress Server Manager does not resubmit that request to that server.
The Dynamic setting is typically the most efficient setting for environments with more
than one QuarkXPress Server instance.
For information about choosing a load-balancing setting, see "Controlling load balancing."
Developers can implement their own load-balancing systems; for more information, see
the QuarkXPress Server Web Integration Guide.
Request timeout interval
QuarkXPress Server Manager attempts to send each request to a QuarkXPress Server instance
that can promptly handle that request. However, in some situations a QuarkXPress Server
instance might be unable to process a request in a reasonable amount of time (for example,
if the server is working on a large rendering job, or if the server computer has stopped
functioning). If you specify a certain period of time as the request timeout interval,
52 | A GUIDE TO QUARKXPRESS SERVER 9.2
QUARKXPRESS SERVER MANAGER