Yes this needs to be addressed. What I would certainly argue against is another
configuration option for purging cache store. Try explaining that to average user :)
Why can't he allocate more memory to target the plateau of projected memory usage? Or
is this some temporary memory spike in his use case that can not be avoided.
On 2010-07-21, at 9:24 AM, Mircea Markus wrote:
Hi,
Eviction thread does two things right now:
- evict stuff from DataContainer
- purge entries from a CacheStore
CacheStore.purge might slow down eviction as it is generally an expensive operation. It
might not even be needed, if the users don't use expiration.
What about:
a) making EvictionThread.purgeCacheStore configurable.
or/and
b) use another thread for purging the store.
This doesn't came out of the blue, there's a user that has eviction+cache store
configured with eviction thread wakeup set to 1 sec - he still gets OOM.
Wdyt?
Cheers,
Mircea
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Vladimir Blagojevic
JBoss Clustering Team
JBoss, by Red Hat