[infinispan-dev] Global components per CacheManager

Mircea Markus mircea.markus at jboss.com
Mon Oct 25 06:39:07 EDT 2010


On 24 Oct 2010, at 21:41, Vladimir Blagojevic wrote:

> User on a forum complained seeing eviction thread per created cache [1].
if user wanted, he can implement a custom ScheduledExecutorFactory that always returns the same single-threaded pool to all caches. So one eviction thread for all the caches associated with the CM.
> Although global configuration settings are shared amongst all caches created in CacheManager each created cache gets a fresh copy of these global elements?!

> Each created cache therefore indeed gets a new eviction executor service with one running thread. Does that mean that by default we also create one async transport executor per cache with 25 threads spinning? 
good point, I think the default async executor pool can be a shared pool.
> 
> If so, we should tell users that running more than two dozen caches per CacheManager is going to impact the system significantly.
> 
> [1] http://community.jboss.org/thread/157913 
> --
> Vladimir Blagojevic
> JBoss Clustering Team
> JBoss, by Red Hat
> 
> 
> 
> 
> 
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev




More information about the infinispan-dev mailing list