Issue description
It is necesasry to introduce priority for jobs. Topincs throttles job execution in order to avoid system overload. A maximum of 10 jobs may currently run at once. This has the effect, that when a less important system executes many long running jobs (> 100) for example OCR on PDFs, any job execution will be stalled for hours.
Developer comments
Introduce an optional parameter priority for scheduling and a store specific priority value.
Introducing priority will not cut it. Let's assume a user scheduled 20 import jobs for time T1, each running for one hour. Once these jobs are started, no other job will be processed until they are all finished. Hmm.
Currently the maximum number of concurrent jobs is globally over all stores. Maybe introducing a store specific maximum of 3 would help. It would at least have prevented the problem that actually occurred a week ago.
Alternatively, one could use the job densitity to throw an exception when the jobs are scheduled.
|
Work sessions
Start |
2023-09-06T07:47:37
|
End |
2023-09-06T08:32:53
|
Participant |
Robert Cerny
|
|