lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] Commented: (LUCENE-730) Restore top level disjunction performance
Date Sat, 26 May 2007 23:44:16 GMT


Hoss Man 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 think it makes more sense to "default" to the most consistent rigidly defined behavior (docs
in order), since that behavior will work (by definition) for any caller regardless of whether
the caller expects the docs in order or not.

people who find performance lacking can then assess their needs and make a conscious choice
to change the setting, and see if it actually improves performance in their use cases.

(ie: "avoid premature optimization" and all that)

> 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