Configuring Number of Concurrent Tasks

You can change the number of tasks that can run concurrently on a Squore Server installation.

If your hardware can handle a higher number of concurrent tasks, you can increase the number of executors by executing the following command (with Squore Server started):

<SQUORE_HOME>/bin/sqadm wildfly ee --core-threads n

Where:

  • n, is the number of concurrent tasks allowed (default value is the number of CPU available for the JVM).

Up to the specified value, long-running tasks can be executed in parallel while others will be placed in a queue to wait until an executor becomes free. A task may be an analysis, a project deletion, etc.

See sqadm wildfly ee manpage to know more.

There is no definitive answer as to what the right number of executors is for a particular environment. The maximum number of concurrent tasks depends on:

  • Project size (how much memory is available for all runs)

  • The number of available threads (the higher the writing limit, the lower the reading response time)

  • The number of CPU intensive Data Providers used in projects, if running on the server

As a rule of thumb, limit the number of concurrent analyses to half the maximum number of threads on the target platform. Since this is platform and project-dependent, some tests should be performed on the target platform in an environment close to production conditions to fine tune this configuration.