lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn Heisey (Commented) (JIRA)" <>
Subject [jira] [Commented] (SOLR-2889) Implement Adaptive Replacement Cache
Date Fri, 11 Nov 2011 15:20:51 GMT


Shawn Heisey commented on SOLR-2889:

Two things:

1) After some thought, I have concluded that a straight LFU cache might fit my needs perfectly,
and it's a baby step towards ARC.

2) I took a quick look at some of the code.  The code for cache trimming and warming is in, but the hits seem to be tracked in {Fast}  I think
this means that the first step would be to refactor things so that we have one or more base
classes with common functionality, which are then extended or imported by smaller classes
that implement LRU, LFU, and ARC.

Am I on the right track?  Does this need another issue?

> Implement Adaptive Replacement Cache
> ------------------------------------
>                 Key: SOLR-2889
>                 URL:
>             Project: Solr
>          Issue Type: New Feature
>          Components: search
>    Affects Versions: 3.4
>            Reporter: Shawn Heisey
>            Priority: Minor
> Currently Solr's caches are LRU, which doesn't look at hitcount to decide which entries
are most important.  There is a method that takes both frequency and time of cache hits into
> If it's feasible, this could be a good addition to Solr/Lucene.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message