The two concurrent maps (for local and remote transactions) use default concurrency levels. Should these be tuneable in <transaction …>, and either way, what should they default to? I really don't think the JDK default (16!) is nearly good enough. I have a benchmark that runs 250 threads and this causes a lot of blocking on these maps. How about <locking concurrencyLevel … > as the default for these maps? Is that good enough in terms of a config parameter, or do we want finer-grained control? Cheers Manik -- Manik Surtani manik(a)jboss.org twitter.com/maniksurtani Lead, Infinispan http://www.infinispan.org _______________________________________________ infinispan-dev mailing list infinispan-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev

On 12-01-12 2:45 PM, Manik Surtani wrote: > > How about<locking concurrencyLevel …>  as the default for these maps?  Is that good enough in terms of a config parameter, or do we want finer-grained control? > +1 lets use existing concurrencyLevel attribute of locking element.