[
https://issues.apache.org/jira/browse/LUCENE-4598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526618#comment-13526618
]
Michael McCandless commented on LUCENE-4598:
--------------------------------------------
bq. Is this really an issue? I thought that pulling a top-level D&PEnum on a
single posting won't gain much by iterating per segment? The per-segment
iteration is more complicated (code-wise) ...
I think it should help somewhat ... I don't expect the gains to be earth
shattering though :)
bq. Anyway, I think that either in this issue or another one, we should explore
a Collector that aggregates the ordinals during collection, and not after
collection has finished. That will save substantial RAM consumed by the bitset
(not critical) and potential float[] (for scores), which is the size of the
result set.
+1, I'll open a new issue for that.
> 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]
