[
https://issues.apache.org/jira/browse/SOLR-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12511024
]
Yonik Seeley commented on SOLR-291:
-----------------------------------
Thanks Koji, this has been in the back of my mind for a long time.
Perhaps the cap should be independent of the queryResultWindowSize... perhaps
something like
<queryResultMaxDocsCached>250<queryResultMaxDocsCached>
that will allow the first number of pages to be cached?
> add "don't cache docList" option
> --------------------------------
>
> Key: SOLR-291
> URL: https://issues.apache.org/jira/browse/SOLR-291
> Project: Solr
> Issue Type: Improvement
> Components: search
> Reporter: Koji Sekiguchi
> Priority: Minor
> Attachments: SOLR-291.patch
>
>
> WHAT:
> A flag "noCacheIfLarger" is added to <queryResultWindowSize/> tag, i.e.
> <queryResultWindowSize noCacheIfLarger="true">50</queryResultWindowSize>. The
> flag can be omitted and the default is false.
> If this flag is set to true and user requires more results (in this case,
> start>=50), SolrIndexSearcher doesn't put the docList into queryResultCache.
> WHY(USE CASE):
> The Solr administrator can calculate *max* memory consumption for filterCache
> and documentCache as follows:
> filterCache: BitDocSet size * max size (cache entries)
> documentCache: average document size * max size (cache entries)
> however, the memory consumtion for queryResultCache is unpredictable.
> With this patch, if the administrator wants to control memory consumtion more
> strict, he can set queryResultWindowSize with noCacheIfLarger="true".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
