Report execution can be balanced across servers to improve performance. As one execution is being processed subsequent report execution calls will be sent to different servers. For each new job, Exago will prioritize the server with the lowest load (according to CPU and memory load) and ratio of running jobs to max jobs allowed. The number of jobs on a server will not exceed the value specified by the simultaneous_jobs_max setting.
NOTE. In versions prior to v2016.2.12, machine load is not taken into account, and jobs are sent to different servers in the order that they are specified ("round-robin").
The following instructions provide an overview for setting up report execution on remote servers:
On each remote server:
NOTE. Multiple scheduler services can point to the same repository.
In the Exago Application:
NOTE. When multiple remote execution hosts are enabled, the Exago application will prioritize the one with the lowest number of queued jobs.
NOTE. When an execution host is used for both scheduling and remote execution, the Exago application will place immediate priority on Remote Execution tasks.