You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Gary Yao (Jira)" <ji...@apache.org> on 2020/02/11 14:41:00 UTC

[jira] [Commented] (FLINK-16001) Avoid using Java Streams in construction of ExecutionGraph

    [ https://issues.apache.org/jira/browse/FLINK-16001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17034501#comment-17034501 ] 

Gary Yao commented on FLINK-16001:
----------------------------------

How much time does it currently take to compute pipelined regions for a very large execution graph, e.g., 100000 execution vertices?

> Avoid using Java Streams in construction of ExecutionGraph
> ----------------------------------------------------------
>
>                 Key: FLINK-16001
>                 URL: https://issues.apache.org/jira/browse/FLINK-16001
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Coordination
>    Affects Versions: 1.10.0
>            Reporter: Jiayi Liao
>            Priority: Major
>
> I think we should avoid {{Java Streams}} in construction of {{ExecutionGraph}} like function {{toPipelinedRegionsSet}} in {{PipelinedRegionComputeUtil}} because the job submission is definitely performance sensitive, especially when {{distinctRegions}} has a large cardinality.
> Also includes some other places in package {{org.apache.flink.runtime.executiongraph}}
> cc [~trohrmann] [~gjy] [~zhuzh] 



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