[
https://issues.apache.org/jira/browse/SOLR-7036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15424808#comment-15424808
]
Charles Draper commented on SOLR-7036:
--------------------------------------
Is it possible to resolve this issue or
https://issues.apache.org/jira/browse/SOLR-4763 and include the fix in trunk?
I've been following both issues almost since their beginnings hoping at each
release that one of them would be resolved and become part of Solr. I've been
using the CollapsingQParserPlugin plus extra code in our workflow as a work
around (
http://stackoverflow.com/questions/24459372/solr-collapsingqparserplugin-with-group-facet-on-style-facet-counts/25519514#25519514
), but would really like to be able to use the builtin grouping mechanism
because it gives correct group facet counts without the work around.
Thanks everyone for all your contributions. Solr is a great product.
> Faster method for group.facet
> -----------------------------
>
> Key: SOLR-7036
> URL: https://issues.apache.org/jira/browse/SOLR-7036
> Project: Solr
> Issue Type: Improvement
> Components: faceting
> Affects Versions: 4.10.3
> Reporter: Jim Musil
> Assignee: Erick Erickson
> Fix For: 5.5, 6.0
>
> Attachments: SOLR-7036.patch, SOLR-7036.patch, SOLR-7036.patch,
> SOLR-7036.patch, SOLR-7036.patch, SOLR-7036.patch, SOLR-7036_zipped.zip,
> jstack-output.txt, performance.txt, source_for_patch.zip
>
>
> This is a patch that speeds up the performance of requests made with
> group.facet=true. The original code that collects and counts unique facet
> values for each group does not use the same improved field cache methods that
> have been added for normal faceting in recent versions.
> Specifically, this approach leverages the UninvertedField class which
> provides a much faster way to look up docs that contain a term. I've also
> added a simple grouping map so that when a term is found for a doc, it can
> quickly look up the group to which it belongs.
> Group faceting was very slow for our data set and when the number of docs or
> terms was high, the latency spiked to multiple second requests. This solution
> provides better overall performance -- from an average of 54ms to 32ms. It
> also dropped our slowest performing queries way down -- from 6012ms to 991ms.
> I also added a few tests.
> I added an additional parameter so that you can choose to use this method or
> the original. Add group.facet.method=fc to use the improved method or
> group.facet.method=original which is the default if not specified.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
