You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2019/11/20 09:25:00 UTC
[jira] [Updated] (FLINK-14811) Replace Java Streams with for-loops
in vertex input checking
[ https://issues.apache.org/jira/browse/FLINK-14811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated FLINK-14811:
-----------------------------------
Labels: pull-request-available (was: )
> Replace Java Streams with for-loops in vertex input checking
> ------------------------------------------------------------
>
> Key: FLINK-14811
> URL: https://issues.apache.org/jira/browse/FLINK-14811
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Affects Versions: 1.10.0
> Reporter: Zhu Zhu
> Assignee: Zhu Zhu
> Priority: Major
> Labels: pull-request-available
>
> Vertex input checking is invoked in lazily triggered scheduling by a FINISHED vertex state update RPC or a {{scheduleOrUpdateConsumers}} RPC.
> Java Streams is used in it, but it should be avoided since it is performance critical code. See ref [1] and [2].
> We should refactor these Java Streams to improve the performance, for both legacy scheduler and NG schedulers.
> cc [~sewen] [~gjy]
> [1] [flink code style guide|https://flink.apache.org/contributing/code-style-and-quality-java.html]
> [2] [discussion & performance test|https://issues.apache.org/jira/browse/FLINK-14735?focusedCommentId=16974209&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16974209] which compares the performance.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)