[ https://issues.jboss.org/browse/ISPN-863?page=com.atlassian.jira.plugin.s... ] Chas Emerick commented on ISPN-863: ----------------------------------- I am entirely unfamiliar with the implementation details and internal architecture of Infinispan that might make an instrumentation-based eviction approach desirable. That said, if a typical objective is to make it so that caches utilize as much available heap as possible, while never provoking an {{OutOfMemoryError}}, that approach sounds incredibly complicated compared to putting entry values in e.g. {{SoftReference}}s. Is there a reason why such an approach is unworkable in Infinispan, or does it represent an orthogonal potential feature (perhaps because eviction strategies have no control over the object model around cache entries, etc)? Obviously, it doesn't address the notion of providing ways to allocate percentages of the max heap to caches, but I wonder if that's actually desirable given typical use cases and the complexity associated with implementing such controls. -- 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