chore(server): queue handlers shouldn't increase concurrency

[mertalev]

Currently, queue handlers add an additional level of concurrency to each job despite taking up an insignificant amount of time. Once queueing is complete, this results in the remaining slower handlers of each processor to have levels of concurrency higher than intended. For instance, object tagging runs 3 jobs at a time despite object detection and image classification each being assigned a concurrency of 1, and 2 videos are transcoded at a time despite a transcode concurrency of 1.

With this PR, queue handlers will no longer offset concurrency.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Comments	Updated (UTC)
immich	⬜️ Ignored (Inspect)			May 21, 2023 7:36pm

[jrasm91]

Can you instead omit the concurrency argument? I think you can actually remove the whole object and just use a single argument for job name too

[mertalev]

Can you instead omit the concurrency argument? I think you can actually remove the whole object and just use a single argument for job name too

Not including it seems to have the default behavior of one level of concurrency per consumer. Setting it to 0 is a workaround suggested from this issue page. (They mention assigning the total concurrency to the first handler and setting the others to 0, but from my testing the behavior is identical to just setting the queue handler concurrency to 0 instead.)