[
https://issues.apache.org/jira/browse/LUCENE-10125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17421512#comment-17421512
]
Adrien Grand commented on LUCENE-10125:
---------------------------------------
For the record I ran async profiler excluding flushes and merges
({./profiler.sh -o flamegraph -d 60 -X "*SegmentMerger*" -X
"*IndexingChain.flush*"}) to see if there's a significant difference, but the
two profiles look very similar. One difference is the addition of
assertSameSchema (LUCENE-9334) but this is only 3% of the time, excluding
flushes and merges (vs. 50% spent on parsing the input data).
> 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
> Assignee: Adrien Grand
> Priority: Minor
> Attachments: LUCENE-10125_hack.patch
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> 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]
