[infinispan-issues] [JBoss JIRA] (ISPN-863) Eviction based on JVM memory utilization

[ https://issues.jboss.org/browse/ISPN-863?page=com.atlassian.jira.plugin.s... ] Robert Stupp commented on ISPN-863: ----------------------------------- I have got some experiences with memory (heap) based eviction. Eviction based on freeMemory()/totalMemory() is too simple - just because you might not be the only thing inside a JVM. And even if you evict the objects (no more references to the objects) the GC might not collect that garbage right when you "think" it does - this process is too complicated as it could be reflected into some simple and fast piece of code - just think about in which generation the evicted objects were (new gen is collected more often as eden space for example) and which types of GC you are currently using. The only solution I imagine is to specify some kind of "occupied heap" settings. There are two solutions that might work: * Estimate the size of an object (graph) by using reflection - expensive * Estimate the size of an object graph using serialization - expensive - but ISPN already performs serialization - it would be possible to remember the serialized size (if using Java serialization) * Estimate the size using Java's Instrumentation interface - not suitable but possible and not that expensive - but might cause conflicts when using profilers -- 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