[
https://issues.jboss.org/browse/ISPN-863?page=com.atlassian.jira.plugin.s...
]
Manik Surtani commented on ISPN-863:
------------------------------------
Are you suggesting using Runtime.freememory() and Runtime.totalMemory()? This would be
dependent on GC cycles though... but yeah, interesting potential. Only, how would you
know when to *stop* evicting? Calling freememory() repeatedly in a loop is no help since
memory freed by evicting would only be reported after a GC cycle.
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