[infinispan-issues] [JBoss JIRA] Commented: (ISPN-863) Eviction based on JVM memory utilization
Dave Marion (JIRA)
jira-events at lists.jboss.org
Thu Jan 6 10:54:22 EST 2011
[ https://issues.jboss.org/browse/ISPN-863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12573851#comment-12573851 ]
Dave Marion commented on ISPN-863:
----------------------------------
Initially, yes, I was thinking of the Runtime methods freeMemory and maxMemory. Chances are that garbage collection will be occurring the closer you are to reaching the defined (-Xmx) limit of the JVM. I think there a couple of ways to implement this. If 85% is the threshold, then stop evicting when memory usage drops below some other threshold (i.e. 80%). Or, I was just looking at the Java 6 API, and it appears that another option would be to use the MemoryPoolMXBean. You could receive notifications when the threshold has been exceeded and after garbage collection has occurred to see what the free memory is. There are some examples of notification and polling mechanisms.
> Eviction based on JVM memory utilization
> ----------------------------------------
>
> Key: ISPN-863
> URL: https://issues.jboss.org/browse/ISPN-863
> Project: Infinispan
> Issue Type: Enhancement
> Components: Eviction
> Affects Versions: 4.2.0.Final
> Environment: N/A
> Reporter: Dave Marion
> Assignee: Manik Surtani
> Labels: eviction, threshold
> Fix For: 5.1.0.BETA1, 5.1.0.Final
>
>
> Allow user to specify percentage threshold upon which eviction will kick in and begin evicting entries based on the specified strategy. This would allow user to create a cache that will attempt to keep as many entries in memory as possible without having to specify maxEntries.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the infinispan-issues
mailing list