lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (LUCENE-7905) Optimizations for OrdinalMap
Date Fri, 14 Jul 2017 15:03:00 GMT


ASF subversion and git services commented on LUCENE-7905:

Commit 3df97d3f0c0e558c52514a7e500afeffe96e795d in lucene-solr's branch refs/heads/master
from Mike McCandless
[;h=3df97d3 ]

LUCENE-7905: optimize how OrdinalMap builds its map

> Optimizations for OrdinalMap
> ----------------------------
>                 Key: LUCENE-7905
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>             Fix For: 7.1
>         Attachments: LUCENE-7905.patch, LUCENE-7905.patch, LUCENE-7905.patch, LUCENE-7905-specialized.patch
> {{OrdinalMap}} is a useful class to quickly map per-segment ordinals to global space,
but it's fairly costly to build, which must typically be done on every NRT refresh.
> I'm using it quite heavily in two different places, one for {{SortedSetDocValuesFacetCounts}},
and another custom usage, and I found some small optimizations to improve its construction
> I switched it to use a simple priority queue to merge the terms instead of the more general
{{MultiTermsEnum}}, which does extra work since it must also provide postings, implement seekExact,
> I also pulled {{OrdinalMap}} out into its own oal.index class.
> When testing construction time for my case the patch is ~16% faster (159.9s -> 134.2s)
in one case with 91.4 M terms and ~9% faster (115.6s -> 105.7s) in another case with 26.6
M terms.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message