lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Busch (JIRA)" <>
Subject [jira] Commented: (LUCENE-730) Restore top level disjunction performance
Date Sun, 27 May 2007 02:00:16 GMT


Michael Busch commented on LUCENE-730:

> The latest patch defaults to docs in order above performance,
> but my personal taste is to have performance by default.

I agree with Hoss here. IMO allowing docs out of order is a big
API change. I think if people switch to 2.2 they just want it
to work as before without having to add special settings. If 
they need better performance for certain types of queries and 
they know that their application can deal with docs out of order
they can enable the faster scoring. 
So my vote is +1 for docs in order by default.

> Some performance tests with prohibited scorers could still
> be needed to find out which of the boolean scorers does better
> on them. 

That'd be helpful. However, I'm currently working on some other
issues. Maybe you or others would have some time to run those

> Restore top level disjunction performance
> -----------------------------------------
>                 Key: LUCENE-730
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Search
>            Reporter: Paul Elschot
>         Assigned To: Michael Busch
>            Priority: Minor
>             Fix For: 2.2
>         Attachments: lucene-730.patch, TopLevelDisjunction20061127.patch
> This patch restores the performance of top level disjunctions. 
> The introduction of BooleanScorer2 had impacted this as reported
> on java-user on 21 Nov 2006 by Stanislav Jordanov.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

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

View raw message