You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "David Boychuck (JIRA)" <ji...@apache.org> on 2014/08/08 20:43:12 UTC

[jira] [Updated] (SOLR-6345) collapsingQParserPlugin degraded performance when using tagging

     [ https://issues.apache.org/jira/browse/SOLR-6345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Boychuck updated SOLR-6345:
---------------------------------

    Description: 
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. I will try to see of the problem can be observed in the unit tests for the collapsingQParserPlugin. I will update with the results.

  was:
I ma 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. I will try to see of the problem can be observed in the unit tests for the collapsingQParserPlugin. I will update with the results.


> 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. I will try to see of the problem can be observed in the unit tests for the collapsingQParserPlugin. I will update with the results.



--
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