[
https://issues.apache.org/jira/browse/SOLR-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Rutherglen updated SOLR-1308:
-----------------------------------
Description:
Solr caches docsets at the top level Multi*Reader level. After a
commit, the filter/docset caches are flushed. Reloading the
cache in near realtime (i.e. commits every 1s - 2min)
unnecessarily consumes IO resources when reloading the filters,
especially for largish indexes.
We'll cache docsets at the SegmentReader level. The cache key
will include the reader.
was:
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.
Summary: Cache docsets at the SegmentReader level (was: Cache docsets
and docs at the SegmentReader level)
I changed the title because we're not going to cache docs in
this issue (though I think it's possible to cache docs by the
internal id, rather than the doc id).
Per-segment facet caching and merging per segment can go into a
different issue.
> Cache docsets 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 at the top level Multi*Reader level. After a
> commit, the filter/docset caches are flushed. Reloading the
> cache in near realtime (i.e. commits every 1s - 2min)
> unnecessarily consumes IO resources when reloading the filters,
> especially for largish indexes.
> We'll cache docsets at the SegmentReader level. The cache key
> will include the reader.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
