[
https://issues.apache.org/jira/browse/SOLR-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495204
]
Hoss Man commented on SOLR-221:
-------------------------------
it might be worth trying to clarify if the performance cliff really results
from being *optimized* or if it's just a result of one of the two traits of an
optimized index: being a single segment, having no deletions.
tuning the behavior based on either of those traits is just as easy as tuning
based on both traits.
Minor point: if we're going to add facet config options, i'd prefer they stay
as standard standard SolrParms that can be defaulted i the handler config (and
theoretically overridden per request) it just seems cleaner to have all
options in one place, and there's not a lot of reason not to when dealing with
options tha don't *need8 to be identicle for every request.
> 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.
