[
https://issues.apache.org/jira/browse/SOLR-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926350#action_12926350
]
Yonik Seeley commented on SOLR-2205:
------------------------------------
bq. I think the only thing to do for the issue is to also port the changes made
in TopGroupCollector to TopGroupSortCollector.
Is that a valid optimization for TopGroupSortCollector though? Given that the
sorts are different, and the sort between groups is based on the *first*
document by group, a document could not be competitive according to "sort", but
could pop to the top of an existing group via "group.sort" and thus cause that
group to move down in the rankings.
This stuff is tricky enough, we still really need to develop some good random
tests to verify any optimizations + corner cases.
> Grouping performance improvements
> ---------------------------------
>
> Key: SOLR-2205
> URL: https://issues.apache.org/jira/browse/SOLR-2205
> Project: Solr
> Issue Type: Sub-task
> Components: search
> Affects Versions: 4.0
> Reporter: Martijn van Groningen
> Fix For: 4.0
>
> Attachments: SOLR-2205.patch, SOLR-2205.patch
>
>
> This issue is dedicated to the performance of the grouping functionality.
> I've noticed that the code is not really performing on large indexes. Doing a
> search (q=*:*) with grouping on an index from around 5M documents took around
> one second on my local development machine. We had to support grouping on an
> index that holds around 50M documents per machine, so we made some changes
> and were able to happily serve that amount of documents. Patch will follow
> soon.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
