lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENE-1847) PhraseQuery/TermQuery/SpanQuery use IndexReader specific stats in their explains
Date Mon, 24 Aug 2009 21:03:59 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12747074#action_12747074
] 

Mark Miller commented on LUCENE-1847:
-------------------------------------

I'm wondering if we should cache the isMethodOverridden now. clazz.getMethod is painfully
slow.

If I keep teeing up a ton of new TermQuery/PhraseQuery/SpanQuery Weights for searching, its
going to be much, much slower in a throughput benchmark.

> PhraseQuery/TermQuery/SpanQuery use IndexReader specific stats in their explains
> --------------------------------------------------------------------------------
>
>                 Key: LUCENE-1847
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1847
>             Project: Lucene - Java
>          Issue Type: Bug
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>            Priority: Minor
>             Fix For: 2.9
>
>         Attachments: LUCENE-1847.patch, LUCENE-1847.patch, LUCENE-1847.patch, LUCENE-1847.patch
>
>
> PhraseQuery uses IndexReader in explainfor top level stats - as mentioned by Mike McCandless
in LUCENE-1837.
> TermQuery uses IndexReader in explain for top level stats
> Always been a bug with MultiSearcher, but per segment search makes it worse.

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


Mime
View raw message