Thread pool configuration

The Thread pool configuration (formerly known as Asynchronous Runner) is a component that manages the execution of background tasks. These background tasks use SIL scripts in a controlled environment separate from the main Jira processes, enabling automated operations to be performed without impacting the performance or stability of the core Jira functionality.

How to access the Thread pool configuration

To access the Thread pool configuration:

Open the Jira admin settings and select Apps.
Go to Power Apps Config > General > Thread pool.

On this page: 1 How to access the Thread pool configuration 2 Key configuration parameters 2.1 Threads 2.2 Maximum Script Runtime 2.3 Checkpoint Interval 3 Monitor and optimize 4 More configuration guides

Key configuration parameters

To optimize your Thread pool configuration for your specific environment and workload requirements, it's essential to understand how each parameter affects the execution and resource consumption of background SIL scripts. Each parameter directly impacts script processing capacity, execution duration limits, and system resource management.

Threads

This is the number of running threads (number of SIL scripts running at the same time). Each script runs as a separate process in the thread pool.

Default value	10 threads
Higher value impact	With a higher number of threads, scripts will complete faster because more scripts can run simultaneously.	This places more demand on system processor and memory resources.
Lower value impact	With a lower number of threads, scripts might need to wait in a queue before processing.	This can delay task completion.

Maximum Script Runtime

This is the maximum amount of time a SIL script can run before it is automatically terminated. This setting prevents scripts from running indefinitely, particularly when they might be waiting on external systems that have stopped responding.

Default value	1 hour
Higher value impact	With a higher Maximum Script Runtime, scripts have more time to complete complex tasks, which is useful for processes that interact with external systems or handle large datasets.	System resources (processors and memory) remain allocated to scripts for longer periods.
Lower value impact	With a lower Maximum Script Runtime, system resources are released more quickly, which is better for environments where resource availability is critical.	This can cause legitimate long-running scripts to terminate before completion.

Checkpoint Interval

This is the interval at which the system checks for and cleans up expired tasks (SIL scripts that exceed the configured Maximum Script Runtime).

The Thread pool is maintained by a watchdog thread — a background process that monitors running scripts and reclaims resources from expired tasks. The Checkpoint Interval determines how often this watchdog performs its checks.

Default value	1 minute
Longer interval impact	With a longer interval, the system checks less frequently for expired tasks, reducing the resource impact of the monitoring process itself.	Resources from terminated scripts may remain allocated longer before being released back to the system.
Shorter interval impact	With a shorter interval, the system checks more frequently for expired tasks, allowing resources to be returned to Jira faster.	The monitoring process itself consumes more system resources with frequent checks.

While Maximum Script Runtime and Checkpoint Interval are configured in hours and minutes respectively, most scripts complete in milliseconds.

Monitor and optimize

The Thread Pool configuration page displays key metrics to help you optimize settings:

Maximum task queue length reached: the highest number of tasks that were waiting to be processed
Current running tasks: the number of scripts currently executing

Use these metrics and considerations to adjust your configuration:

Thread pool size	If your number of threads is consistently below the maximum queue length, consider increasing the thread pool size For reporting tasks that gather data from multiple sources, increase threads if the pool is frequently at capacity
Maximum Scrip Runtime	For long-running tasks (like complex reports or multi-system integrations), increase the maximum runtime Ensure resource-intensive tasks have sufficient time to complete without termination

By regularly monitoring these metrics and applying these guidelines, you can maintain optimal performance while ensuring all your background tasks complete successfully.