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

Adrien Grand updated LUCENE-6815:
---------------------------------
    Attachment: LUCENE-6815.patch

Updated patch to work with the new Scorer API.

luceneutil likes it better as well (bulk scoring was disabled on boolean 
queries for this run):

{noformat}
                    TaskQPS baseline      StdDev   QPS patch      StdDev        
        Pct diff
            OrNotHighLow      836.69      (4.3%)      829.89      (4.2%)   
-0.8% (  -8% -    8%)
                 Prefix3       36.35      (5.0%)       36.27      (4.7%)   
-0.2% (  -9% -    9%)
              HighPhrase       51.03      (3.5%)       50.99      (3.9%)   
-0.1% (  -7% -    7%)
             MedSpanNear       14.14      (2.1%)       14.15      (2.4%)    
0.1% (  -4% -    4%)
         LowSloppyPhrase       29.65      (2.5%)       29.68      (2.5%)    
0.1% (  -4% -    5%)
               LowPhrase       18.98      (2.3%)       19.02      (3.2%)    
0.2% (  -5% -    5%)
                  IntNRQ        8.07      (6.5%)        8.09      (6.4%)    
0.2% ( -11% -   14%)
               MedPhrase       37.46      (2.1%)       37.54      (2.4%)    
0.2% (  -4% -    4%)
                 LowTerm      657.15      (8.1%)      658.77      (8.6%)    
0.2% ( -15% -   18%)
            HighSpanNear       10.35      (3.4%)       10.39      (3.7%)    
0.4% (  -6% -    7%)
            OrHighNotMed       57.75      (6.1%)       57.97      (6.4%)    
0.4% ( -11% -   13%)
        HighSloppyPhrase        3.09      (6.4%)        3.10      (6.3%)    
0.4% ( -11% -   14%)
             AndHighHigh      104.21      (2.2%)      104.63      (1.9%)    
0.4% (  -3% -    4%)
                Wildcard      139.23      (4.0%)      139.82      (4.8%)    
0.4% (  -7% -    9%)
            OrNotHighMed      160.13      (3.7%)      161.04      (3.2%)    
0.6% (  -6% -    7%)
                 MedTerm      196.83      (5.1%)      198.03      (4.9%)    
0.6% (  -8% -   11%)
         MedSloppyPhrase       28.51      (3.0%)       28.69      (2.6%)    
0.6% (  -4% -    6%)
              AndHighMed      199.74      (2.9%)      201.03      (2.1%)    
0.6% (  -4% -    5%)
           OrNotHighHigh       52.47      (4.0%)       52.81      (3.7%)    
0.6% (  -6% -    8%)
              AndHighLow      831.21      (5.2%)      836.72      (4.4%)    
0.7% (  -8% -   10%)
                HighTerm      106.80      (4.9%)      107.52      (4.5%)    
0.7% (  -8% -   10%)
           OrHighNotHigh       49.22      (4.2%)       49.58      (4.9%)    
0.7% (  -7% -   10%)
            OrHighNotLow       72.74      (6.9%)       73.36      (7.2%)    
0.9% ( -12% -   16%)
             LowSpanNear       40.43      (1.7%)       40.86      (2.0%)    
1.1% (  -2% -    4%)
                 Respell       85.26      (4.0%)       86.34      (2.6%)    
1.3% (  -5% -    8%)
                  Fuzzy1       76.05     (12.4%)       77.99     (14.1%)    
2.6% ( -21% -   33%)
              OrHighHigh       21.18      (5.5%)       22.00      (5.6%)    
3.9% (  -6% -   15%)
               OrHighMed       44.83      (5.4%)       46.73      (6.2%)    
4.2% (  -6% -   16%)
               OrHighLow       53.74      (5.3%)       56.55      (5.7%)    
5.2% (  -5% -   17%)
                  Fuzzy2       49.00     (14.4%)       51.79      (9.5%)    
5.7% ( -15% -   34%)
{noformat}

> Should DisjunctionScorer advance more lazily?
> ---------------------------------------------
>
>                 Key: LUCENE-6815
>                 URL: https://issues.apache.org/jira/browse/LUCENE-6815
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Adrien Grand
>            Assignee: Adrien Grand
>            Priority: Minor
>         Attachments: LUCENE-6815.patch, LUCENE-6815.patch, LUCENE-6815.patch
>
>
> Today if you call DisjunctionScorer.advance(X), it will try to advance all 
> sub scorers to X. However, if DisjunctionScorer is being intersected with 
> another scorer (which is almost always the case as we use BooleanScorer for 
> top-level disjunctions), we could stop as soon as we find one matching sub 
> scorer, and only advance the remaining sub scorers when freq() or score() is 
> called. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to