Page History

By default, Unimus executes up to 100 concurrent jobs of each type.
(job types are: "discovery", "backup", "config_push", "network_scan")

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

...

-Dunimus.server.core.discovery-thread-pool-core-size=10
-Dunimus.server.core.discovery-thread-pool-max-size=10

-Dunimus.server.core.backup-thread-pool-core-size=10
-Dunimus.server.core.backup-thread-pool-max-size=10

-Dunimus.server.core.push-thread-pool-core-size=10
-Dunimus.server.core.push-thread-pool-max-size=10

-Dunimus.server.core.scan-thread-pool-core-size=10
-Dunimus.server.core.scan-thread-pool-max-size=10

In the above example, we configured Unimus to perform a maximum of 10 concurrent jobs of each type.

If you use Unimus Core, the Unimus server will propagate these settings to each Core - so configuring this is needed only on the Unimus server.
(please note each core will use it's own thread pools for jobs - in effect, this configures job concurrency per Core)