Maximum Number of Processes and Connections

You can set the maximum number of processes and connections.

For the report service and the batch report service, you can set the maximum number of processes and the maximum number of high affinity and low affinity connections that the dispatcher can open to handle requests. For the agent, Content Manager, delivery, job, and report data services, you can set the maximum number of connections.

There are separate settings for peak and non-peak hours. For more information, see Setting usage peak periods.

Maximum Number of Connections

There is a maximum of one of each of these services per dispatcher: agent, Content Manager, delivery, job, report data. Connections handle one request from one service at a time.

You can specify the maximum number of connections for each service during peak periods and non-peak periods using the following settings:

Maximum connections for <service_name> service during non-peak period
Maximum connections for <service_name> service during peak period

The default number of connections is four.

Maximum Number of Processes

There can be multiple report service and batch report service processes on each dispatcher. You can specify the maximum number of processes during peak periods using the following settings:

Maximum number of processes for the <service_name> during peak period
Maximum number of processes for the <service_name> during non-peak period

The default number of processes for each service is two.

Affinity Connections

Report servers accept low and high affinity connections to process requests from the batch report and report services.

Low affinity requests can be handled by any report server. Typically, low affinity requests are used when a report run is initially requested.

High affinity requests are ideally handled by a specific report server. Typically, high affinity requests are for reports that were already requested and may include actions, such as going to the next page in a report. If the specific report server is not available or busy, then the report is rerun (low affinity request) on any report server and the next page (high affinity request) is directed to that server.

Affinity settings take precedence over balance request settings and advanced routing settings. For more information, see Balancing requests among dispatchers and Dispatcher routing.

If affinity settings are changed for a service while entries are running, the number of server processes could double. The number of processes may temporarily exceed the maximum setting while the change takes effect. This may cause problems if your system does not have enough memory for the interim period.

You can specify the number of low and high affinity connections for the report service and the batch report service using the following setting:

Number of <low | high> affinity connections for the <service_name> during non-peak period

Note: Although the wording of this setting implies that it applies to non-peak periods only, it applies to both non-peak periods and peak periods.

For batch report service, the default number of low affinity connections is two. For the report service, the default number of low affinity connections is four. The default number of high affinity connections for all services is one.