By default, Unimus executes up to 100 concurrent jobs of each type.
(job types areall device operations concurrently (in parallel), up to a configured limit.
All job requests started by the users or by any schedule are queued, and executors then process jobs from the appropriated queues.
Unimus currently separates jobs into 4 job-specific queues: "discovery", "backup", "config_push", "network_scan".
Default configuration allows for 100 concurrent jobs for each executor (queue) from "discovery", "backup" and "config_push".
The "network_scan" executor by default allows for 20 concurrent jobs, with each IP being scanned consuming one job.
For example:
- if you run a Discovery on 5 devices, all 5 devices will be discovered in parallel.
- if you run a Config Push on 200 devices, Unimus will start pushing to 100 devices in parallel, and continue pushing with up to 100 maximum parallel sessions until the Push finishes on all devices
Unimus uses perthread pools for as the executors for the per-job-type thread pools for executing jobsqueues. By affecting the size of the thread pools, you can change how many concurrent (parallel) jobs Unimus executes.
(this will in turn also affect how many maximum concurrent outbound SSH / Telnet sessions Unimus opens to your devices)
...