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
{{ message }}
This repository has been archived by the owner on Dec 13, 2023. It is now read-only.
Currently I have a polling system for each task I want to execute in the worker, which looks for a new task, if there is one, executes it, and then waits for a while to continue the cycle.
This is not efficient since I cannot execute 20 tasks of the same type for example (I only do 1 polling - execution - wait per task type).
Is there any system for my worker to listen for tasks, take them if it recognizes them, up to a limit of number of tasks?
Something consumer style?
Or the only way to do it is as I am doing, with polling?
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
-
Currently I have a polling system for each task I want to execute in the worker, which looks for a new task, if there is one, executes it, and then waits for a while to continue the cycle.
This is not efficient since I cannot execute 20 tasks of the same type for example (I only do 1 polling - execution - wait per task type).
Is there any system for my worker to listen for tasks, take them if it recognizes them, up to a limit of number of tasks?
Something consumer style?
Or the only way to do it is as I am doing, with polling?
Beta Was this translation helpful? Give feedback.
All reactions