[
https://issues.apache.org/jira/browse/FLINK-31745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Nowojski closed FLINK-31745.
----------------------------------
Resolution: Not A Problem
It just restored performance back to the level from ~12th Jan probably yet
another "unexplained" performance change, that has something todo with either
environment, or JIT compiler, or sth like that
The suspected commit range
{noformat}
git ls 9190ea9624..f3b63b7c96
f3b63b7c962 [2 weeks ago] [FLINK-31656][runtime][security] Obtain delegation
tokens early to support external file system usage in blob server [Gabor
Somogyi]
6c1ffe544e3 [9 days ago] [FLINK-31690][python] Fix KeyedCoProcessFunction to
set the current key into the context [Dian Fu]
6101ad313be [10 days ago] [FLINK-31688][docs] Fix the broken links in docs for
Azure Table Storage [Yuxin Tan]
9e83858c7dc [12 days ago] [FLINK-31652][k8s] Handle the deleted event in case
pod is deleted during the pending phase [sunxia]
{noformat}
reveals nothing relevant in that range.
> Performance regression on serializerHeavyString since April 3rd
> ---------------------------------------------------------------
>
> Key: FLINK-31745
> URL: https://issues.apache.org/jira/browse/FLINK-31745
> Project: Flink
> Issue Type: Bug
> Reporter: Martijn Visser
> Priority: Blocker
> Fix For: 1.18.0
>
>
> serializerHeavyString baseline=241.682406 current_value=203.24132
> http://codespeed.dak8s.net:8000/timeline/#/?exe=1&ben=serializerHeavyString&extr=on&quarts=on&equid=off&env=2&revs=200
--
This message was sent by Atlassian Jira
(v8.20.10#820010)