In that case a "pulling" queue might not be the best approach.
Am Donnerstag, 3. Juli 2014 16:27:10 UTC+2 schrieb Jeremy Burns:
-- You can only try to shorten the timeout between "lookups".
A better approach would be a "push notification" approach.
Maybe some other queues provide that service?
mark
Am Donnerstag, 3. Juli 2014 16:27:10 UTC+2 schrieb Jeremy Burns:
I just set up the CakePHP Queue plugin (https://github.com/dereuromark/cakephp-queue ) and it works great. I'm building a messaging app where messages and replies are distributed via web sockets. Before the plugin the model layer was emitting the messages after save, which introduced a delay for the sending user while the web socket worked. With the plugin that delay goes as the messages are queued and emitted in a different process.
The challenge I have now is that - as I want the messages to be emitted instantly - my cron job is set up as:
* * * * * cd path/to/app && Console/cake Queue.Queue runworker
…because even a second delay is too long. This is killing the CPU, which is running at 100%.
What is the recommended config for both the queue.php config file and cron job so that I get instant processing without CPU burn?
Like Us on FaceBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP
---
You received this message because you are subscribed to the Google Groups "CakePHP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cake-php+unsubscribe@googlegroups.com.
To post to this group, send email to cake-php@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment