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/07/20 21:18:05 UTC
[jira] [Commented] (LUCENE-6668) Optimize SortedSet/SortedNumeric
storage for the few unique sets use-case
[ https://issues.apache.org/jira/browse/LUCENE-6668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633964#comment-14633964 ]
Robert Muir commented on LUCENE-6668:
-------------------------------------
+1, nice to have TABLE applied to the other types here too!
> Optimize SortedSet/SortedNumeric storage for the few unique sets use-case
> -------------------------------------------------------------------------
>
> Key: LUCENE-6668
> URL: https://issues.apache.org/jira/browse/LUCENE-6668
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Adrien Grand
> Assignee: Adrien Grand
> Priority: Minor
> Attachments: LUCENE-6668.patch, LUCENE-6668.patch
>
>
> Robert suggested this idea: if there are few unique sets of values, we could build a lookup table and then map each doc to an ord in this table, just like we already do for table compression for numerics.
> I think this is especially compelling given that SortedSet/SortedNumeric are our two only doc values types that use O(maxDoc) memory because of the offsets map. When this new strategy is used, memory usage could be bounded to a constant.
--
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