[jboss-jira] [JBoss JIRA] Commented: (JBCACHE-971) Eviction policy based on adaptive replacement
Paul Cowan (JIRA)
jira-events at lists.jboss.org
Thu Jun 12 19:49:00 EDT 2008
[ http://jira.jboss.com/jira/browse/JBCACHE-971?page=comments#action_12416943 ]
Paul Cowan commented on JBCACHE-971:
------------------------------------
For the record (Manik's recent target version change reminded me to update this): I have now developed a cache library which includes implementations of the following algorithms:
* ARC
* FRC (non-self-adjusting version of ARC; not sure if this is covered by the same patents as ARC)
* 2Q
* MQ (Multi-Queue Replacement, by Zhou, Philbin and Li -- see http://www.usenix.org/event/usenix01/full_papers/zhou/zhou_html/index.html -- I am not sure if there are any patent encumbrances here, and have contacted 2 of the authors to try and find out)
This library has been developed without being jboss-specific; I have produced an adapter for JBoss Cache 1.3 (which we're still stuck using) and then one for JBoss Cache 2.0, which I would be happy to contribute (my employer has given me permission to do so, and is in the process of formalising this internally).
HOWEVER, I have not heard anything back from IBM in the last 5 months in relation to the ARC patent issues, which makes me loathe to release this (of course!). Is there anyone at JBoss who would be in a better position to shake the IBM tree and try to extract an answer? I would be very keen to release my library and think JBoss Cache would benefit from it.
> Eviction policy based on adaptive replacement
> ---------------------------------------------
>
> Key: JBCACHE-971
> URL: http://jira.jboss.com/jira/browse/JBCACHE-971
> Project: JBoss Cache
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Eviction
> Reporter: Manik Surtani
> Assigned To: Mircea Markus
> Fix For: 3.1.0
>
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> Quote from Mircea Markus:
> There is an eviction policy algorithm more efficient than LRU (which I found quite popular) - Adaptive Replacement Policy. The basic idea is to not rely only on the time of last access to the node, but also on the number of time(frequency) a given node was accessed. Here it is a nice description of how it works: http://en.wikipedia.org/wiki/Adaptive_Replacement_Cache.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list