[
https://issues.apache.org/jira/browse/SOLR-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12735159#action_12735159
]
Yonik Seeley commented on SOLR-1308:
------------------------------------
Absolutely! We need to get 1.4 out of the way first of course.
One interesting question is the structure of the cache and how to size caches.
One way: if someone specifies a document cache of 128 docs, and we have a cache
per segment, how big should each segment cache be?
One answer is that if a segment represents 10% of the total index, then it
should get 10% of the cache. There are downsides to that though - it fails to
take into account non-uniform access in the index (hotspots).
> 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.
