[ 
https://issues.apache.org/jira/browse/SOLR-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13259301#comment-13259301
 ] 

Shawn Heisey commented on SOLR-3393:
------------------------------------

After all the bugs are worked out of the implementation covered by this issue, 
I can see a future scenario where the existing (slow) LFUCache is scrapped, 
FastLFUCache is renamed LFUCache, and a new FastLFUCache implementation that 
uses a Concurrent class is created.  If the committers would prefer that I go 
ahead and scrap LFUCache now and just use that name, let me know.

I have no plans to work on SOLR-2889, so it may be best to just close that 
issue.  I don't know if SOLR-2906 should be changed from a subtask to a full 
task.

                
> Implement an optimized LFUCache
> -------------------------------
>
>                 Key: SOLR-3393
>                 URL: https://issues.apache.org/jira/browse/SOLR-3393
>             Project: Solr
>          Issue Type: Improvement
>          Components: search
>    Affects Versions: 3.6, 4.0
>            Reporter: Shawn Heisey
>            Priority: Minor
>             Fix For: 4.0
>
>
> SOLR-2906 gave us an inefficient LFU cache modeled on 
> FastLRUCache/ConcurrentLRUCache.  It could use some serious improvement.  The 
> following project includes an Apache 2.0 licensed O(1) implementation.  The 
> second link is the paper (PDF warning) it was based on:
> https://github.com/chirino/hawtdb
> http://dhruvbird.com/lfu.pdf
> Using this project and paper, I will attempt to make a new O(1) cache called 
> FastLFUCache that is modeled on LRUCache.java.  This will (for now) leave the 
> existing FastLFUCache/ConcurrentLFUCache implementation in place.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to