[FLINK-28241] Massive regression on 20.06.2021

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Component/s: Benchmarks
• Labels: pull-request-available
• Assignee: Anton Kalashnikov
• Reporter: Anton Kalashnikov
• Created: 24/Jun/22 08:14
• Updated: 27/Jun/22 06:17
• Resolved: 27/Jun/22 06:17

Description

In FLINK-27921 added property `REQUIREMENTS_CHECK_DELAY` that optimizes the number of checks of resources but it also leads to a little delay during the init phase which is totally not critical for the normal scenario. But unfortunately, our benchmarks can not exclude the time of the initial phase(or shutdown phase) from the total time of benchmarks. As result, all benchmarks, that have a relatively short execution time(compare to the initial phase time), have regression(up to 50%). As a quick solution, it makes sense just to set `REQUIREMENTS_CHECK_DELAY` to zero for all benchmarks.
Not full list of affected benchmarks:

• asyncWait
• globalWindow
• mapSink
• readFileSplit
• remoteRebalance
• serializer*
• sorted*
• twoInputOneIdleMapSink

Issue Links

• is caused by: FLINK-27921 Introduce the checkResourceRequirementsWithDelay in DeclarativeSlotManager
• is related to: FLINK-28243 Considering only time of targeted operation for calculation benchmarks performance
• links to: GitHub Pull Request #56