Yeah sleep is not the solution here. You will need to implement the solution in your queue handler. One solution is to keep a global counter in cache and if the count has exceeded X calls per second, don't process the job, instead just release back into the queue.
@rickshawhobo Thanks for your reply. So, it seems we need to manually handle the circumstance.
Anyway, I'm still wondering why this is not supported out of the box. Do I misunderstand how the queue works? I mean is it okay if I just run all the jobs continuously?
Sign in to participate in this thread!
Laravel
Laravel News
Laracasts
Laravel Podcast