[rabbitmq-discuss] Publisher confirms performance

[Matthias Radestock]

Allen,

On 11/09/12 21:40, Allen Riddle wrote:
> I'm using Ruby and a rudimentary AMQP client that doesn't do any
> buffering.

There is always buffering, e.g. in the OS network layer.

> I don't think I had a great enough understanding of confirms when I
> started this, it sounds like it's only beneficial over transactions
> if you can receive the confirms asynchronously. Is that true?

There is no difference between publishing a bunch of messages and then

a) waiting until all have been confirmed, or

b) issuing a tx.commit and waiting for the commit-ok


Regards,

Matthias.