[
https://issues.apache.org/jira/browse/LUCENE-4598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526627#comment-13526627
]
Shai Erera commented on LUCENE-4598:
------------------------------------
bq. That will save substantial RAM consumed by the bitset (not critical)
"not critical" can become very critical for very large indexes. I am now
talking to a team who index 1B documents with Lucene (very small documents). A
bitset that size will consume 128MB RAM, that's substantial !
Thanks for opening the issue. Though, if we move to only during-collection
aggregation, I don't think that this issue will still be valid. Only if we keep
ScoredDocIdsCollector, and perhaps the two-pass is efficient in some cases.
> Facet aggregation should work per segment
> -----------------------------------------
>
> Key: LUCENE-4598
> URL: https://issues.apache.org/jira/browse/LUCENE-4598
> Project: Lucene - Core
> Issue Type: Improvement
> Components: modules/facet
> Reporter: Michael McCandless
>
> Currently the facet module uses MultiFields.* to pull the D&PEnum in
> PayloadIterator, to access the payloads that store the facet ords.
> It then makes heavy use of .advance and .getPayload to visit all docIDs in
> the result set.
> I think we should get some speedup if we go segment by segment instead ...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
