...
Understanding Joget Deadline
Let's assume there are 100 pending instances where their deadline has matured.
If Assuming the "System Settings > Process Deadline Checker Interval" is set to 1 hour, Joget will check and run all each of the 100 pending instances in batches of 10.
Once all 100 instances have been processed, it will then wait based on the Process Deadline Checker Interval, which in this case is 1 hour. And the cycle repeats itself.
10 per batch, complete all the processes, then wait 1 hour (that's the interval). Repeat this cycle and run all pending instances, on completion wait 1 hour then repeat the cycle. If the Joget server has many pending processes, the cycle time will be longer and may push the next cycle to start at a later time. BTW setting
| Warning | ||
|---|---|---|
| ||
Setting a short 1-second internal time may increase the CPU load and data IO in your Joget server, which may cause a performance hit. We would recommend an internal timer of 30 seconds or longer. |
| Info |
|---|
In Joget DX, as an added benefit, you can use Multi Tools Process Tool to run threads concurrently. For any deadline tasks that are not relevant to data integrity, you can wrap those tools used in deadline within Multi-Tools & select the "Run Mode" property to "Run tools concurrently in multiple threads". This can improve the Joget performance. |
...