[
https://issues.apache.org/jira/browse/LUCENE-10125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17420735#comment-17420735
]
Adrien Grand commented on LUCENE-10125:
---------------------------------------
This was faster than expected since it's easy to identify whether the commit is
good or bad after a couple merges. The bad change is this one:
https://github.com/apache/lucene/pull/102, which consists of writing directly
to the directory instead of using an unnecessary intermediate
ByteBuffersDataOutput. cc [~ivera]
[~uschindler] Maybe this is due to the thing that we discussed the other day,
that FSIndexOutput doesn't optimize writing float/double/short/int/long
directly?
> Investigate indexing throughput regression on NYC Taxis between 2021-04-12
> and 2021-05-24
> -----------------------------------------------------------------------------------------
>
> Key: LUCENE-10125
> URL: https://issues.apache.org/jira/browse/LUCENE-10125
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Adrien Grand
> Priority: Minor
>
> There's been a significant drop in indexing throughput between 2021-04-12 and
> 2021-05-24 on the NYC Taxis benchmark. Unfortunately several suspects have
> been merged during that period of time so we might need to git bisect to
> figure out which one is responsible for the regression. Interestingly the
> sorted index looks less affected than the non-sorted indexes.
> https://home.apache.org/~mikemccand/lucenebench/sparseResults.html#index_throughput
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
