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

Shalin Shekhar Mangar commented on SOLR-667:
--------------------------------------------

bq. For apples to apples load tests, this more then doubled my overall 
throughput. 
Very good to hear that!

bq. Is this the cleanup involved when hitting a high-water mark?
Yes, a cleanup is attempted when the size crosses the high watermark ('size' 
config parameter). It is done in two stages. In the first stage, least recently 
used items are evicted. If, after the first stage, the cache size is still 
greater than 'acceptableSize' config parameter (default is 0.95*maxSize), the 
second stage takes over. The second stage is more intensive and tries to bring 
down the cache size to the 'minSize' config parameter (default is 0.9*maxSize).

Note that the cleanup is done in the same thread which calls a put on the 
cache, hence the 'pulsing' that you are seeing. The cache implementation 
supports using a separate cleanup thread too, however it is not used currently. 
We still need to evaluate the best way to use it and how much it can help.

> Alternate LRUCache implementation
> ---------------------------------
>
>                 Key: SOLR-667
>                 URL: https://issues.apache.org/jira/browse/SOLR-667
>             Project: Solr
>          Issue Type: New Feature
>          Components: search
>    Affects Versions: 1.3
>            Reporter: Noble Paul
>            Assignee: Shalin Shekhar Mangar
>             Fix For: 1.4
>
>         Attachments: ConcurrentLRUCache.java, ConcurrentLRUCache.java, 
> ConcurrentLRUCache.java, SOLR-667.patch, SOLR-667.patch, SOLR-667.patch, 
> SOLR-667.patch, SOLR-667.patch, SOLR-667.patch
>
>
> The only available SolrCache i.e LRUCache is based on _LinkedHashMap_ which 
> has _get()_ also synchronized. This can cause severe bottlenecks for faceted 
> search. Any alternate implementation which can be faster/better must be 
> considered. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to