[
https://issues.apache.org/jira/browse/LUCENE-3972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13701060#comment-13701060
]
Paul Masurel commented on LUCENE-3972:
--------------------------------------
(e-commerce Solr user here)
We hit the very same performance hit with pathological queries with
1M+ unique groups and need to solve this issue for our business.
Would an hybrid approach switching implementation half-ways when
the number of unique groups detected gets too high be welcomed?
I also wonder whether the number of segments plays a great role in this.
Did you observe that in your benchmarking?
> Improve AllGroupsCollector implementations
> ------------------------------------------
>
> Key: LUCENE-3972
> URL: https://issues.apache.org/jira/browse/LUCENE-3972
> Project: Lucene - Core
> Issue Type: Improvement
> Components: modules/grouping
> Reporter: Martijn van Groningen
> Attachments: LUCENE-3972.patch, LUCENE-3972.patch
>
>
> I think that the performance of TermAllGroupsCollectorm,
> DVAllGroupsCollector.BR and DVAllGroupsCollector.SortedBR can be improved by
> using BytesRefHash to store the groups instead of an ArrayList.
--
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
