[rabbitmq-discuss] detecting publish failure across restart

Sylvain Hellegouarch sh at defuze.org
Tue Jun 1 12:35:55 BST 2010

On Mon, May 31, 2010 at 10:30 PM, David Wragg <david at rabbitmq.com> wrote:

> Hi Sylvain,
> Sylvain Hellegouarch <sh at defuze.org> writes:
> > I'm curious, in the general case, what's the cost of using a transaction?
> > Does it consume more resources? Roughly, what takes place within
> > RabbitMQ?
> There is indeed a cost associated with a transaction.  One source of
> overhead is the fact that the AMQP tx.commit method is synchronous, and
> so involves a round-trip over the network to the server.  Another is the
> fact that when the server commits a transaction, it must make sure that
> the relevant effects of a transaction have reached stable storage
> (e.g. that a persistent message that reaches a queue has been stored on
> disk).  My colleagues might be able to list other costs.
> It's difficult to quantify these costs in general, but I think its fair
> to say that they have a significant impact compared with
> non-transactional uses of AMQP.  The MulticastMain tool included with
> our Java client library has command line options that allow the impact
> to be measured in various scenarios.
> David

Cheers for that feedback. Much appreciated. I will try to perform some
measurements and see both the server and client behave.

- Sylvain
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20100601/29e50079/attachment.htm 

More information about the rabbitmq-discuss mailing list