You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Michael McCandless (JIRA)" <ji...@apache.org> on 2015/06/22 18:51:00 UTC
[jira] [Commented] (LUCENE-6548) Optimize BlockTree's
Terms.intersect a bit for "very finite" automata
[ https://issues.apache.org/jira/browse/LUCENE-6548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14596208#comment-14596208 ]
Michael McCandless commented on LUCENE-6548:
--------------------------------------------
I'll commit the last patch soon; I think there are other things we can do here, but we can explore them later and this is already a good speedup, at lease in the "very finite" (arcs that typically have only one label, not a range) automata intersect case.
> Optimize BlockTree's Terms.intersect a bit for "very finite" automata
> ---------------------------------------------------------------------
>
> Key: LUCENE-6548
> URL: https://issues.apache.org/jira/browse/LUCENE-6548
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: 5.3, Trunk
>
> Attachments: LUCENE-6548.patch, LUCENE-6548.patch, LUCENE-6548.patch
>
>
> I've been digging into why BlockTree's Terms.intersect impl is slower for a "very finite" union-of-terms test over random IDs (LUCENE-3893) and I found a few performance improvements that at least for that one use case gets a ~11% speedup.
--
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