JobQueue Task Processing

Hello Community!

We needed to create a large number of tasks for adding users to an access group. These tasks were successfully generated in the JobQueue, but their execution took an excessive amount of time. As a result, other tasks running on the same job server remained stuck in the Loaded status and did not progress.

Notably, the job server handling these tasks showed minimal resource utilization—averaging only 15% RAM and 20% CPU usage despite available capacity.

To address this, I followed recommendations to adjust the Number of external slots and Number of internal slots in the Job Destination settings. Initially configured as:

    External slots: 10

    Internal slots: 48

We increased both values to 500, but this change had no effect:

    Resource utilization remained unchanged (~15% RAM / 20% CPU).

    Task processing speed did not improve.

Question:
Could this indicate that:

    The wrong settings were modified?

    Additional configurations are required to force the job server to leverage more resources and accelerate task processing?

We’re using version 9.2.

Any insights or suggestions would be greatly appreciated.

Parents
  • I wanted to mention that increasing External slots and Internal slots is reflected in the job server’s web interface (under Running/forwarding instances). However, in the Process step cache line, there is an entry like 1000 Ready / 10 Running (as an example).

    Question:
    How can we make the job server process these tasks faster?

Reply
  • I wanted to mention that increasing External slots and Internal slots is reflected in the job server’s web interface (under Running/forwarding instances). However, in the Process step cache line, there is an entry like 1000 Ready / 10 Running (as an example).

    Question:
    How can we make the job server process these tasks faster?

Children
No Data