I have a question regarding the performance of the task scheduler.
I couldn’t find any topic about CPU multithreading.
- Used Zammad version: 5.1.1
- Used Zammad installation type: package
- Operating system: CentOS 7
- Browser + version: Firefox v102
Have a fast execution of tasks modifying more than 500 tickets in the scheduler (at least, use a larger CPU percentage of the machine)
A task that modifies about 1000 tickets (700/1100/2000+ for testing) in the scheduler runs in about 5 minutes, and ticket changes are visible after about 30 minutes.
The “top” utility indicates 100% utilization (single thread) for the zammad user’s ruby command (script?) when the task is being performed (drops to 0% when finished).
Total CPU usage does not exceed 16% (8 Threads).
Create a task in the scheduler which aims to modify a “select” field on a large selection of tickets (1000+).
Example: all tickets in the “open” state in group A are moved to group B with the state “new”.
Have a 4+ thread cpu machine and check the performance monitor (does not exceed 1 thread).
To simply ask: Do you know if it is possible to enable multithreading on zammad’s ruby scripts?
I have also observed that tasks modifying more than 2000 tickets show the correct number of modified elements, but only really modify 2000 (tickets are not modified from 2001+).
A ticket on Github is already open, so I won’t talk about it here.