You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Zhilong Hong (Jira)" <ji...@apache.org> on 2021/03/11 07:44:00 UTC

[jira] [Created] (FLINK-21731) Add a benchmark for DefaultScheduler#startScheduling

Zhilong Hong created FLINK-21731:
------------------------------------

             Summary: Add a benchmark for DefaultScheduler#startScheduling
                 Key: FLINK-21731
                 URL: https://issues.apache.org/jira/browse/FLINK-21731
             Project: Flink
          Issue Type: Improvement
          Components: Benchmarks, Runtime / Coordination
    Affects Versions: 1.13.0
            Reporter: Zhilong Hong
             Fix For: 1.13.0


We notice that {{DefaultScheduler#allocateSlotsAndDeploy}} is not covered in the current scheduler benchmark. When we are trying to implement a benchmark related to this procedure, we think that it's better to implement a benchmark that covers the entire {{DefaultScheduler#startScheduling}} procedure instead.

This can avoid missing any parts that may affect the performance of scheduling. Also in this way we don't need to add benchmarks for every sub-procedure related to scheduling, which makes the benchmark heavy and hard to maintain. Then we can just focus on the performance-sensitive procedures, as the existing benchmarks do.

The new benchmark item is implemented based on {{DefaultSchedulerBatchSchedulingTest}}.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)