You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Robert Muir (JIRA)" <ji...@apache.org> on 2015/04/14 11:45:12 UTC
[jira] [Commented] (LUCENE-6421) Add two-phase support to
MultiPhraseQuery
[ https://issues.apache.org/jira/browse/LUCENE-6421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14493849#comment-14493849 ]
Robert Muir commented on LUCENE-6421:
-------------------------------------
final result:
{noformat}
Report after iter 19:
Chart saved to out.png... (wd: /home/rmuir/workspace/util/src/python)
Task QPS trunk StdDev QPS patch StdDev Pct diff
MultiPhraseHHH 0.35 (6.3%) 0.35 (5.7%) 2.2% ( -9% - 15%)
MultiPhraseHHL 17.21 (1.8%) 17.65 (1.3%) 2.6% ( 0% - 5%)
MultiPhraseHHM 5.12 (2.8%) 5.42 (1.9%) 5.7% ( 1% - 10%)
MultiPhraseMMH 33.71 (2.9%) 39.70 (1.2%) 17.8% ( 13% - 22%)
MultiPhraseMML 160.35 (1.5%) 201.54 (1.4%) 25.7% ( 22% - 29%)
MultiPhraseMMM 72.26 (2.2%) 95.67 (2.0%) 32.4% ( 27% - 37%)
{noformat}
> Add two-phase support to MultiPhraseQuery
> -----------------------------------------
>
> Key: LUCENE-6421
> URL: https://issues.apache.org/jira/browse/LUCENE-6421
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Robert Muir
> Attachments: LUCENE-6421.patch, LUCENE-6421_luceneutil.patch
>
>
> Two-phase support currently works for both sloppy and exact Scorers but it does not work if you have multiple terms at the same position (MultiPhraseQuery).
> This is because UnionPostingsEnum.nextDoc() aggressively reads and merges all the positions. Even making this initialization lazy might just be enough?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org