[
https://issues.apache.org/jira/browse/FLINK-32686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17747733#comment-17747733
]
Wencong Liu edited comment on FLINK-32686 at 7/27/23 3:42 AM:
--------------------------------------------------------------
Thanks for reporting this. The second regression since 07.24 is caused by
commit id: c9e1833642650e0b1ea162371dd7c6d35f2e21b7. The commit disables the
repair in FLINK-32094 unexpectedly and causes the regression in 07.24. I'll
open a pull request to fix this. The first regression in 07.09 is not related
with FLINK-32094.
was (Author: JIRAUSER281639):
Thanks for reporting this. The second regression since 07.24 is caused by
commit id: c9e1833642650e0b1ea162371dd7c6d35f2e21b7. The commit disables the
repair in [FLINK-32094] startScheduling.BATCH performance regression since May
11th - ASF JIRA (apache.org) unexpectedly and causes the regression in 07.24.
I'll open a pull request to fix this. The first regression in 07.09 is not
related with FLINK-32094.
> Performance regression on startScheduling.BATCH and startScheduling.STREAMING
> since 2023-07-24
> -----------------------------------------------------------------------------------------------
>
> Key: FLINK-32686
> URL: https://issues.apache.org/jira/browse/FLINK-32686
> Project: Flink
> Issue Type: Bug
> Affects Versions: 1.18.0
> Reporter: Martijn Visser
> Priority: Blocker
> Labels: pull-request-available
>
> http://codespeed.dak8s.net:8000/timeline/#/?exe=5&ben=startScheduling.STREAMING&extr=on&quarts=on&equid=off&env=2&revs=200
> http://codespeed.dak8s.net:8000/timeline/#/?exe=5&ben=startScheduling.BATCH&extr=on&quarts=on&equid=off&env=2&revs=200
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
