[
https://issues.apache.org/jira/browse/LUCENE-2111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851508#action_12851508
]
Michael McCandless commented on LUCENE-2111:
--------------------------------------------
bq. Awesome work! What changes make those queries run faster with the default
codec? Mostly terms dict changes and automaton for fuzzy/wildcard?
The AutomatonQuery (for fuzzy/wildcard) gives the biggest gains :) Other MTQs
(prefix) see gains I think because of more efficient terms enum. The TermQuery
speedup surprises me -- that can't be a terms dict thing (just one lookup); i'm
not sure offhand why it's faster. That code is not very different than trunk.
bq. How's the indexing performance?
Unchanged -- I indexed first 10M docs of wikipedia and the times were nearly
identical.
> Wrapup flexible indexing
> ------------------------
>
> Key: LUCENE-2111
> URL: https://issues.apache.org/jira/browse/LUCENE-2111
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Index
> Affects Versions: Flex Branch
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: 3.1
>
> Attachments: benchUtil.py, flex_backwards_merge_912395.patch,
> flex_merge_916543.patch, flexBench.py, LUCENE-2111-EmptyTermsEnum.patch,
> LUCENE-2111-EmptyTermsEnum.patch, LUCENE-2111.patch, LUCENE-2111.patch,
> LUCENE-2111.patch, LUCENE-2111.patch, LUCENE-2111.patch, LUCENE-2111.patch,
> LUCENE-2111.patch, LUCENE-2111.patch, LUCENE-2111.patch, LUCENE-2111.patch,
> LUCENE-2111.patch, LUCENE-2111.patch, LUCENE-2111.patch, LUCENE-2111.patch,
> LUCENE-2111.patch, LUCENE-2111.patch, LUCENE-2111.patch, LUCENE-2111.patch,
> LUCENE-2111.patch, LUCENE-2111.patch, LUCENE-2111_bytesRef.patch,
> LUCENE-2111_experimental.patch, LUCENE-2111_fuzzy.patch,
> LUCENE-2111_mtqNull.patch, LUCENE-2111_mtqTest.patch,
> LUCENE-2111_toString.patch
>
>
> Spinoff from LUCENE-1458.
> The flex branch is in fairly good shape -- all tests pass, initial search
> performance testing looks good, it survived several visits from the Unicode
> policeman ;)
> But it still has a number of nocommits, could use some more scrutiny
> especially on the "emulate old API on flex index" and vice/versa code paths,
> and still needs some more performance testing. I'll do these under this
> issue, and we should open separate issues for other self contained fixes.
> The end is in sight!
--
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: [email protected]
For additional commands, e-mail: [email protected]
