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.

On Thu, Nov 28, 2013 at 5:28 PM, Mircea Markus <mmarkus@redhat.com> wrote:

Hi Fassela,

In future please post these kind of questions on the infinsipan forum so that other can benefit from them as well ;)

On Nov 28, 2013, at 10:08 AM, Faseela K <faseela.k@ericsson.com> wrote:

> Hello,
>
> Is there any limitation on the number of infinispan caches that can be created, in a clustered environment?

I know users that created thousands, I'm not aware of an upper bound but creating a cache certainly brings it cost.

>
> Also, is there any performance difference between the below two cases :
>
> Case 1 : Constructing a cache with 10000 entries
> Case 2 : Splitting the above cache into 100 caches of 100 entries.
>
> Entry count is same in both the cases, but will there be any significant performance overhead in creating 100 caches?

creating the cache has it's cost, but once it is created, the performance should be pretty much the same.

>
> Thanks,
> Faseela
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev

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

_______________________________________________
infinispan-dev mailing list
infinispan-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev