[infinispan-dev] rethinking ISPN transactions

Mircea Markus mmarkus at redhat.com
Fri Nov 29 09:39:09 EST 2013


On Nov 21, 2013, at 3:18 PM, Dan Berindei <dan.berindei at gmail.com> wrote:

> Hmm, couldn't you just disable recovery in the TM to get the same performance with a XA resource as with a synchronization?
> 

I don't think that would be enough actually. Even without recovery, for transactions (XA) that have more than one participant registered, the TM writes information on the transaction log.
This is a persistent log and writing to it slows down things.


> 
> On Thu, Nov 21, 2013 at 1:57 PM, Pedro Ruivo <pedro at infinispan.org> wrote:
> 
> 
> On 11/21/2013 11:34 AM, Galder Zamarreño wrote:
> >
> >
> > It's way faster actually. The speed difference from all the extra work required by Transaction Manager to deal with multiple XA resources, make transactions recoverable..etc. We've done tests in the past (i.e. Hibernate 2LC) comparing both and the difference was quite big.
> >
> 
> you are right. I forgot the recovery mechanism :)
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
> 
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev

Cheers,
-- 
Mircea Markus
Infinispan lead (www.infinispan.org)







More information about the infinispan-dev mailing list