Over a million developers have joined DZone.

Faster transaction protocols in Infinispan!

DZone's Guide to

Faster transaction protocols in Infinispan!

· Performance Zone ·
Free Resource

Built by operators for operators, the Sensu monitoring event pipeline empowers businesses to automate their monitoring workflows and gain deep visibility into their multi-cloud environments. Get started for free today.

The total order based protocol is a lock free multi-master scheme (i.e. all the Infinispan nodes are able to execute read and write transactions) commit protocol. This protocol relies on the concept of totally ordered delivery of messages which, informally, implies that each node which delivers a set of messages, delivers them in the same order.
This protocol comes with this advantages.
  1. transactions can be committed in one phase, as they are delivered in the same order by the nodes that receive them.
  2. it mitigates distributed deadlocks.
The weaknesses of this approach are the fact that its implementation relies on a single thread per node which delivers the transaction and its modification, and the slightly higher number of messages exchanged by JGroups.
Thus, this protocol delivers best performance in scenarios of  high contention, in which it can benefit from the single-phase commit and the deliver thread is not the bottleneck.
Currently, the Total Order based protocol is available only in  transactional caches for  replicated and  distributed modes and it is available in  Infinispan 5.3.0 Alpha1.
If you are interested in know more, please take a look at the user documentation where it is explained in more details how it behaves and how you can configure it. Since this is a recent work, if you find any incorrect behavior please create a JIRA.
Following we have some benchmark evaluation comparing the total order based implementation with the locking based implementation in two different scenarios:
  • Contention: 1000 keys in a shared pool, 8 threads per node and 5 writes (on average) per transaction;
  • No Contention: 1000 keys in a thread private pool, 8 threads per node and 5 writes (on average) per transaction.

Download our guide to mitigating alert fatigue, with real-world tips on automating remediation and triage from an IT veteran.


Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}