You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@lucene.apache.org by "Bruno Roustant (Jira)" <ji...@apache.org> on 2019/12/02 09:38:00 UTC

[jira] [Assigned] (LUCENE-9045) Do not use TreeMap/TreeSet in BlockTree and PerFieldPostingsFormat

     [ https://issues.apache.org/jira/browse/LUCENE-9045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruno Roustant reassigned LUCENE-9045:
--------------------------------------

    Assignee: Bruno Roustant

> Do not use TreeMap/TreeSet in BlockTree and PerFieldPostingsFormat
> ------------------------------------------------------------------
>
>                 Key: LUCENE-9045
>                 URL: https://issues.apache.org/jira/browse/LUCENE-9045
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Bruno Roustant
>            Assignee: Bruno Roustant
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> TreeMap/TreeSet is a heavy structure designed to dynamically sort keys. It's iterator is much less performant than a list iterator. We should not use it when we don't need the sorting capability once built.
> And this is the case in BlockTreeTermsReader and PerFieldPostingsFormat. We need a Map and to sort keys at building time. But once built, we don't need to sort anymore, we can use a simple list for iteration efficiency.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org