[
https://issues.apache.org/jira/browse/FLINK-23560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Nowojski reopened FLINK-23560:
------------------------------------
The issue in
http://codespeed.dak8s.net:8000/timeline/?ben=sortedTwoInput&env=2
http://codespeed.dak8s.net:8000/timeline/?ben=sortedMultiInput&env=2
still persists. It looks like there were two different performance regressions
in the same commit range. Which makes sense, because my and [~akalashnikov]'s
fix for the first regression couldn't explain those {{sortedInput}} benchmarks
as:
# those benchmarks are so slow (2M records/s) and involve spilling to disk,
that any regression around enqueuing mailbox action shouldnt’ be visible
# those benchmarks are using FLIP-27 sources, so no problem with biased locking
as described by [~akalashnikov]
> Performance regression on 29.07.2021
> ------------------------------------
>
> Key: FLINK-23560
> URL: https://issues.apache.org/jira/browse/FLINK-23560
> Project: Flink
> Issue Type: Bug
> Components: Benchmarks
> Affects Versions: 1.14.0
> Reporter: Piotr Nowojski
> Assignee: Piotr Nowojski
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.14.0
>
> Attachments: Screenshot 2021-07-30 at 15.46.54.png
>
>
> http://codespeed.dak8s.net:8000/timeline/?ben=remoteFilePartition&env=2
> http://codespeed.dak8s.net:8000/timeline/?ben=uncompressedMmapPartition&env=2
> http://codespeed.dak8s.net:8000/timeline/?ben=compressedFilePartition&env=2
> http://codespeed.dak8s.net:8000/timeline/?ben=tupleKeyBy&env=2
> http://codespeed.dak8s.net:8000/timeline/?ben=arrayKeyBy&env=2
> http://codespeed.dak8s.net:8000/timeline/?ben=uncompressedFilePartition&env=2
> http://codespeed.dak8s.net:8000/timeline/?ben=sortedTwoInput&env=2
> http://codespeed.dak8s.net:8000/timeline/?ben=sortedMultiInput&env=2
> http://codespeed.dak8s.net:8000/timeline/?ben=globalWindow&env=2
> (And potentially other benchmarks)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
