Impact of enabling "invocationBatching" without using it

[fertroya]

Hi,

I'm currently checking the infinispan configuration of one of our clients and detected they've set up  <invocationBatching enabled="true" /> at default level.

In java code though, they never make use of cache.startBatch() / catch.endBatch().

My question is simple: does that configuration take any effect on the application's behaviour without explicitly invoking batching methods?

Judging by the official docs, setting it up and not using it is bogus http://infinispan.org/docs/5.1.x/user_guide/user_guide.html#_batching

Thank you in advance,

[mircea.markus]

I guess you have the autocommit attribute[1] set to true (which is the default). What happens is that infinispan starts and completes a transaction for each operation you perform. Disable autocmmit and you should get an exception.

[1] http://infinispan.org/docs/6.0.x/user_guide/user_guide.html#_backward_compatibility

[fertroya]

Oh sorry, I think I didn't make myself clear.

This is an excerpt of the configuration:

<default>
         ...
        <invocationBatching enabled="true" />
        <transaction transactionMode="TRANSACTIONAL" ..>
        </transaction>
        ...
 </default>

I forgot to mention we're using INFINISPAN 5.1.5 which, as you mention, has autoCommit enabled by default.

What I want to know is if declaring invocationBatching here makes any sense; given that in java code no batchs are created and that transactionMode is already declared as TRANSACTIONAL.

Cheers

[mircea.markus]

What I want to know is if declaring invocationBatching here makes any sense; given that in java code no batchs are created and that transactionMode is already declared as TRANSACTIONAL.

No, it doesn't help. If anything it slows down things - shouldn't be noticeable though.

I strongly recommend moving to a newer inifinispan version: there's been a lot of performance and functionality improvements since 5.1.x