[rabbitmq-discuss] Expected msg/s per CPU core
michael.s.klishin at gmail.com
Sun May 19 12:40:21 BST 2013
2013/5/19 Nikola Savic <niks at osic.rs>
> With every execution, PHP scripts connects to RabbitMQ and post 1-3
So the consumer apps are constantly being terminated, started, then they
connect and consume
messages (I assume using basic.get)? That's far from being very efficient,
really built with long-running apps in mind.
Plus, with basic.get and immediate processing you get one message at a
time. With "push API"
consumers it can be multiple messages at once. See
I don't really know what to recommend besides at least not reconnecting all
the time. AFAIK php clients
only support basic.get and not "push" deliveries, neither a long-running
PHP process can offer any
way of concurrent processing.
You can try fetching multiple messages before you process them.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss