[
https://issues.jboss.org/browse/ISPN-4132?page=com.atlassian.jira.plugin....
]
Dan Berindei commented on ISPN-4132:
------------------------------------
Eviction in Infinispan assumes that evicted entry can be easily restored, either by
Infinispan loading them from a store or by the user application itself. With that
assumption, it doesn't make sense to evict a bunch of keys all at once: just because
session S has been accessed recently, it doesn't mean that attribute S.A has also been
accessed recently and it's worth keeping it in memory.
Group-based eviction
--------------------
Key: ISPN-4132
URL:
https://issues.jboss.org/browse/ISPN-4132
Project: Infinispan
Issue Type: Feature Request
Components: Eviction
Affects Versions: 6.0.2.Final
Reporter: Paul Ferraro
Assignee: Dan Berindei
Currently, Infinispan only supports size-based eviction. We can configure a cache with
a specific max-entries, so if the size exceeds this value infinispan will evict any
surplus entries.
However, if the cache has grouping enabled, it is perhaps more useful to use group-based
eviction. In this scenario, max-entries would be interpreted as "max-groups",
and infinispan would evict entire groups of cache entries if the number of groups exceeds
this value.
In WildFly, web sessions make use of grouping. A single web session will map to a single
group of multiple cache entries, where the number of entries is not necessarily the same
for a given session. In this case, evicting per cache entry does not make sense - all
entries of a session should be evicted or not at all. Also, users can specify the max
number of sessions they want to remain in memory. Until infinispan supports group-based
eviction, translating this value to an appropriate max-entries is cumbersome and
imprecise.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira