[
https://issues.apache.org/jira/browse/SOLR-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496046
]
J.J. Larrea commented on SOLR-221:
----------------------------------
Clearly Solr is going to end up with more than 2 algorithms for computing
facets, and there's no reason to think they won't be able to happily coexist in
SimpleFacets. And we will surely need additional control parameters even for
the 2.5 (with your patch) algorithms now in place. So I think we should
establish a convention for separating algorithm-specific parameters so we don't
end up with a jumble of top-level parameters.
So rather than facet.minDfFilterCache, how about:
facet.enum.cache.minDF (enable term enum cache for terms with docFreq >
minDF)
f.<field>.facet.enum.cache.minDF
Might it not be useful to turn off term enum caching when the number of terms
was above a certain maximum, even if the minDF criterion is met, to trade
cycles for memory when neither the field cache nor filter cache is practicable?
In that case, it could be:
facet.enum.cache.maxTerm (enable term enum cache for fields where numTerms
<= maxTerm)
> faceting memory and performance improvement
> -------------------------------------------
>
> Key: SOLR-221
> URL: https://issues.apache.org/jira/browse/SOLR-221
> Project: Solr
> Issue Type: Improvement
> Reporter: Yonik Seeley
> Assigned To: Yonik Seeley
> Attachments: facet.patch
>
>
> 1) compare minimum count currently needed to the term df and avoid
> unnecessary intersection count
> 2) set a minimum term df in order to use the filterCache, otherwise iterate
> over TermDocs
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
