[rabbitmq-discuss] pika/puka

Laing, Michael michael.laing at nytimes.com
Thu Jan 2 20:12:45 GMT 2014

pika doesn't use threads.

You can do your own event loop by writing a connector...

However the tornado event loop is plenty fast, or libev if you are
adventurous (9.14).

They are both significantly faster than select (the default).

We use the libev connector in our AMQP/sockjs/websocket gateway launching
today (fully deployed next week).

Where we don't need a combined event loop, we use tornado, which is more


On Thu, Jan 2, 2014 at 10:52 AM, bernhard <bs at bit-field.de> wrote:

> Hello,
> allow me a beginners question. I played a bit with the pika examples to
> see, if I can use amqp in my own projects. Everything looks very
> promising for me.
> But I did not find a way, to do my own event loop. Then I found puka,
> which exposes the raw socket fd and allows for own event loops. Looks
> very nice for me too. But it seems to be unsupported for a long time.
> The reason, why I want my own event loop, is that I want to avoid
> threads (no, I don't want to start a flame war; just my personal style).
> And I want to be informed by events from external devices (connected by
> serial, ethernet, ...) very fast. So adding the fds to the select()
> seems natural for me.
> Did I explore pika not good enough (I read about the asynchronous parts,
> but as far, as I see, it is not, what I need)? Or is puka maintained
> somewhere I didn't look?
> Do have any hints for me?
> Thank you.
> Bernhard
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140102/9ade5ff0/attachment.html>

More information about the rabbitmq-discuss mailing list