You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "James Dyer (JIRA)" <ji...@apache.org> on 2013/05/29 16:45:20 UTC

[jira] [Commented] (SOLR-4874) Investigate "maxCollationTries" correct use of filtercache with "fq"

    [ https://issues.apache.org/jira/browse/SOLR-4874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13669314#comment-13669314 ] 

James Dyer commented on SOLR-4874:
----------------------------------

From: Andy Lester [mailto:andy@petdance.com] 
Sent: Tuesday, May 28, 2013 2:29 PM
To: solr-user@lucene.apache.org
Subject: Why do FQs make my spelling suggestions so slow?

I'm working on using spellcheck for giving suggestions, and collations
are giving me good results, but they turn out to be very slow if
my original query has any FQs in it.  We can do 100 maxCollationTries
in no time at all, but if there are FQs in the query, things get
very slow.  As maxCollationTries and the count of FQs increase,
things get very slow very quickly.

         1    10    20    50   100 MaxCollationTries
0FQs     8     9    10    11    10
1FQ     11   160   599  1597  1668
2FQs    20   346  1163  3360  3361
3FQs    29   474  1852  5039  5095
4FQs    36   589  2463  6797  6807
All times are QTimes of ms.  With spellcheck off I get 8ms for 4fq query.  I can do maxCollation = maxCollationTries = 100 and it comes back in 14ms, so long as I have FQs off.  Add a single FQ and it becomes 13499ms.  I can do maxCollation = maxCollationTries = 1000 and it comes back in 45ms, so long as I have FQs off.  Add a single FQ and it becomes 62038ms.

Here's a query that I've been using as a test:
df=title_tracings_t&
fl=flrid,nodeid,title_tracings_t&
q=bagdad+AND+diaries+AND+-parent_tracings:(bagdad+AND+diaries)&
spellcheck.q=bagdad+AND+diaries&
rows=4&
wt=xml&
sort=popular_score+desc,+grouping+asc,+copyrightyear+desc,+flrid+asc&
spellcheck=true&
spellcheck.dictionary=direct&
spellcheck.onlyMorePopular=false&
spellcheck.count=15&
spellcheck.extendedResults=false&
spellcheck.collate=true&
spellcheck.maxCollations=10&
spellcheck.maxCollationTries=50&
spellcheck.collateExtendedResults=true&
spellcheck.alternativeTermCount=5&
spellcheck.maxResultsForSuggest=10&
debugQuery=off&
fq=((grouping:"1"+OR+grouping:"2"+OR+grouping:"3")+OR+solrtype:"N")&
fq=((item_source:"F"+OR+item_source:"B"+OR+item_source:"M")+OR+solrtype:"N")&
fq={!tag%3Dgrouping}((grouping:"1"+OR+grouping:"2")+OR+solrtype:"N")&
fq={!tag%3Dlanguagecode}(languagecode:"eng"+OR+solrtype:"N")&

Do the collation internals not handle
FQs correctly?  The lookup/hit counts on filterCache seem to be
increasing just fine.  It will do N lookups, N hits, so I'm not
thinking that caching is the problem.
                
> Investigate "maxCollationTries" correct use of filtercache with "fq"
> --------------------------------------------------------------------
>
>                 Key: SOLR-4874
>                 URL: https://issues.apache.org/jira/browse/SOLR-4874
>             Project: Solr
>          Issue Type: Bug
>          Components: spellchecker
>    Affects Versions: 4.3
>            Reporter: James Dyer
>            Priority: Minor
>
> User is reporting much-bigger-than-linear growth in qtime when increasing "maxCollationTries" when there are multiple "fq" parameters in the query.

--
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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org