lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Elschot (JIRA)" <>
Subject [jira] Commented: (LUCENE-365) [PATCH] Performance improvement to DisjunctionSumScorer
Date Wed, 18 Oct 2006 07:31:36 GMT
    [ ] 
Paul Elschot commented on LUCENE-365:

That was indeed not intentional, thanks for adding it back.

To my surprise the svn update applied cleanly on here, and these tests still pass here:

ant -Dtestcase="TestBool*" test
ant -Dtestcase="TestDis*" test

> [PATCH] Performance improvement to DisjunctionSumScorer
> -------------------------------------------------------
>                 Key: LUCENE-365
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Search
>    Affects Versions: CVS Nightly - Specify date in submission
>         Environment: Operating System: other
> Platform: Other
>            Reporter: Paul Elschot
>         Assigned To: Yonik Seeley
>             Fix For: 2.1
>         Attachments:,, DisjunctionSumScorer20061017.patch,,
> A recent profile of the new BooleanScorer2 showed that 
> quite a bit of CPU time is spent in the advanceAfterCurrent method 
> of DisjunctionScorer, and in the PriorityQueue of scorers that 
> is used there. 
> This patch reduces the internal overhead of DisjunctionScorer 
> to about 70% of the current one (ie. 30% saving in cpu time). 
> It also reduces the number of calls to the subscorers, but 
> that was not measured. 
> To get this, it was necessary to specialize the PriorityQueue 
> for a Scorer and to add move some code fragments from DisjunctionScorer 
> to this specialized queue.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message