You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Joel Bernstein (JIRA)" <ji...@apache.org> on 2014/08/08 21:13:12 UTC
[jira] [Commented] (SOLR-6345) collapsingQParserPlugin degraded
performance when using tagging
[ https://issues.apache.org/jira/browse/SOLR-6345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14091176#comment-14091176 ]
Joel Bernstein commented on SOLR-6345:
--------------------------------------
You will see a performance hit when you use tag and exclude because Solr needs to regenerate the DocSet. So, the query needs to be re-run. If Collapsing is part of the query, then collapsing is re-run also. Would be interesting to put some timing statements in the FacetComponent, where it recreates the docset for tag/exclude, to see long this is taking.
> collapsingQParserPlugin degraded performance when using tagging
> ---------------------------------------------------------------
>
> Key: SOLR-6345
> URL: https://issues.apache.org/jira/browse/SOLR-6345
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.7.2
> Reporter: David Boychuck
> Priority: Critical
> Labels: collapsingQParserPlugin
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> I am having a problem with degraded performance when using the collapseQParserPlugin with facet tagging.
> An example query would look something like this
> {code}
> http://host:port/solr/index/handler?facet=true&fq={!collapse field=groupid}&facet.query={!ex=Width_numeric}Width_numeric:[10+TO+15]&facet.query={!ex=Width_numeric}Width_numeric:[15+TO+20]&facet.sort=index&start=0&q=36+x+42+shower+base&fq={!tag%3DWidth_numeric}Width_numeric:[35+TO+40]
> {code}
> When I either remove the grouping
> {code}
> fq={!collapse field=groupid}
> {code}
> or remove the tag
> {code}
> &fq={!tag%3DWidth_numeric}Width_numeric:[35+TO+40]
> {code}
> I am getting requests orders of magnitude faster. In my production environment with around 800k documents. I jump from less than 20ms to over 100ms sometimes 200ms using the collapsingQParserPlugin with tagging.
> The issue can be observed in the TestCollapseQParserPlugin tests:
> {code}
> params.add("q", "*:*");
> params.add("fq", "{!collapse field=group_s}");
> params.add("defType", "edismax");
> params.add("bf", "field(test_ti)");
> params.add("facet", "true");
> params.add("facet.field", "{!ex=test_ti}test_ti");
> params.add("fq", "{!tag=test_ti}test_ti:10");
> assertQ(req(params), "*[count(//doc)=3]",
> "//result/doc[1]/float[@name='id'][.='2.0']",
> "//result/doc[2]/float[@name='id'][.='6.0']"
> );
> {code}
> With this test with the tagging I ran 10 tests and consistently got response times between 23-28ms. When I removed the tag and ran 10 more tests I consistently got results between 15-18ms
> In all cases if I don't use the collapseQParserPlugin with tagging by either removing the tag or leaving the tag but removing the collapse I am getting poor performance.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org