You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am having four different queues listening and running separate operations as typical queues do. Currently if each queue get one job all these four jobs would start processing at once and just on a single worker. I don't want to do this as each queue is resource intensive.
I can't merge all these four jobs into single queue to fix this concurrency issue. The reason is, I am using Arena and would like to see all the jobs separated by the queues like Arena let you see.
Do I have any other approach I can take to solve this problem?
This discussion was converted from issue #2023 on April 26, 2021 08:41.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I am having four different queues listening and running separate operations as typical queues do. Currently if each queue get one job all these four jobs would start processing at once and just on a single worker. I don't want to do this as each queue is resource intensive.
I can't merge all these four jobs into single queue to fix this concurrency issue. The reason is, I am using Arena and would like to see all the jobs separated by the queues like Arena let you see.
Do I have any other approach I can take to solve this problem?
Beta Was this translation helpful? Give feedback.
All reactions