Hi Faseela,
Are you using only the Map API or also using Query or maybe plan
adding it later? If so, then needlessly splitting the data into
multiple smaller caches might became a problem for Query because
it is not capable to search across multiple caches at the same
time. If your domain requires queries across multiple caches
you'll have to execute it manually on each one and collect the
results - quite a nuissance. This point is strictly from Query
standpoint; ignore if it's not in your use case.
Cheers,
Adrian
On 11/29/2013 04:41 AM, Faseela K wrote:
Hi Dan,
I am not using any
transactions that span across multiple caches.
Thanks,
Faseela
There is some extra cost if you have transactions
that span multiple caches: each cache is registered as a
separate XA resource with the Transaction Manager. With a single
cache, there would be a single prepare/commit RPC, regardless of
how many keys the transaction modified. With multiple caches,
there are as many prepare and commit RPCs as there are caches
touched by the transaction.
_______________________________________________
infinispan-dev mailing list
infinispan-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev