[
https://issues.apache.org/jira/browse/FLINK-22773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhu Zhu closed FLINK-22773.
---------------------------
Resolution: Done
Done via
656901beb4617c356840e9ae677ad2c9e65fd8da
2cfbf35649acb78711790ff67f9043835907b8ac
4c7bc08807e03e025c761ac107d7625e689eb6a8
5d77c191cec26147941d1ea06804901bc4c344a1
> 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
> Assignee: Zhilong Hong
> Priority: Major
> Labels: pull-request-available
> 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)
