[rabbitmq-discuss] Publisher confirms requires seperate call to get ack?

[Ryan Brown]

<<Sorry. Finger hit cmd-enter>>

So, in testing the use of publisher confirms in RabbitMQ I am seeing a
significant (many orders of magnitude) decrease in performance when
requesting publisher confirms. Based on my interpretation of the
documentation, it appears that, in order to confirm each message queued was
written to disc, I need to make a request to get the acknowledgment. In
doing so, my publishing rates look like this:

Without publisher confirms:

~11k/mps

With publisher confirms (including call for ack):

187/mps

I feel that I must be doing something wrong. The servers hosting RabbitMQ
are quite robust with 16 cores, 32gb RAM and SSD drives.

Is anybody aware of a good example doing publisher confirms, preferably in
erlang but any language will do. Also, is it necessary to do it for each
message? I know, theoretically, the answer is no. But I have a wrapper
around Rabbit that must return synchronously to clients publishing messages
so it appears to be the best option.

Thanks in advance for any help.

Best.


On Tue, Dec 17, 2013 at 4:06 PM, Ryan Brown <ryankbrown at gmail.com> wrote:

> So, in testing the use of publisher confirms in RabbitMQ I am seeing a
> significant (many orders of magnitude) decrease in performance when
> requesting publisher confirms. Based on my interpretation of the
> documentation, it appears that, in order to confrim each message queued was
> written to disc, I need to make a re
>
> --
> -rb
>



-- 
-rb
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20131217/47eecb75/attachment.html>