[
https://issues.apache.org/jira/browse/LUCENE-7474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15548127#comment-15548127
]
Adrien Grand commented on LUCENE-7474:
--------------------------------------
All our benchmarks use dense data I think. The good news is that these changes
did not seem to slow down indexing in the dense case if I look at
http://people.apache.org/~mikemccand/geobench.html#index-times or
http://people.apache.org/~mikemccand/lucenebench/indexing.html, or at least the
slow down is small enough so that nothing is noticeable if there are points or
terms indexed too. However regarding search, this change is almost certainly
going to make things slower (see eg.
http://people.apache.org/~mikemccand/lucenebench/Term.html), I think we need to
be careful about keeping the slowdown contained.
> Improve doc values writers
> --------------------------
>
> Key: LUCENE-7474
> URL: https://issues.apache.org/jira/browse/LUCENE-7474
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Adrien Grand
> Assignee: Adrien Grand
> Priority: Minor
> Fix For: master (7.0)
>
> Attachments: LUCENE-7474.patch
>
>
> One of the goals of the new iterator-based API is to better handle sparse
> data. However, the current doc values writers still use a dense
> representation, and some of them perform naive linear scans in the nextDoc
> implementation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
