You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Zhu Zhu (Jira)" <ji...@apache.org> on 2021/07/29 02:48:00 UTC
[jira] [Updated] (FLINK-22773) Optimize the construction of
pipelined regions
[ https://issues.apache.org/jira/browse/FLINK-22773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhu Zhu updated FLINK-22773:
----------------------------
Fix Version/s: 1.14.0
> Optimize the construction of pipelined regions
> ----------------------------------------------
>
> Key: FLINK-22773
> URL: https://issues.apache.org/jira/browse/FLINK-22773
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
> Affects Versions: 1.13.0
> Reporter: Zhilong Hong
> Priority: Major
> Fix For: 1.14.0
>
>
> During the initialization of DefaultExecutionTopology, pipelined regions will be computed for scheduling. Currently the complexity of this procedure is O(N^2):
>
> {code:java}
> for all vertices in the topology:
> for all consumed results of the vertex:
> if the consumed result is reconnectable:
> merge the current region with its producer region
> {code}
> One possible solution is mentioned in FLINK-17330.
> If we can optimize this procedure from O(N^2) to O(N), it will speed up the initialization of SchedulerNG, and accelerate the submission of a new job, especially for OLAP jobs.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)