lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Rutherglen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SOLR-1308) Cache docsets and docs at the SegmentReader level
Date Wed, 02 Dec 2009 07:00:21 GMT

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

Jason Rutherglen commented on SOLR-1308:
----------------------------------------

I'm taking a look at this, it's straightforward to cache and
reuse docsets per reader in SolrIndexSearcher, however, we're
passing docsets all over the place (i.e. UnInvertedField). We
can't exactly rip out DocSet without breaking most unit tests,
and writing a bunch of facet merging code. We'd likely lose
functionality? 

Will the MultiDocSet concept SOLR-568 as an easy way to get
something that works up and running? Then we can benchmark and
see if we've lost performance?

> Cache docsets and docs at the SegmentReader level
> -------------------------------------------------
>
>                 Key: SOLR-1308
>                 URL: https://issues.apache.org/jira/browse/SOLR-1308
>             Project: Solr
>          Issue Type: Improvement
>    Affects Versions: 1.4
>            Reporter: Jason Rutherglen
>            Priority: Minor
>             Fix For: 1.5
>
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> Solr caches docsets and documents at the top level Multi*Reader
> level. After a commit, the caches are flushed. Reloading the
> caches in near realtime (i.e. commits every 1s - 2min)
> unnecessarily consumes IO resources, especially for largish
> indexes.
> We can cache docsets and documents at the SegmentReader level.
> The cache settings in SolrConfig can be applied to the
> individual SR caches.

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


Mime
View raw message