You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Xu Pingyong (JIRA)" <ji...@apache.org> on 2017/04/21 01:02:04 UTC
[jira] [Commented] (FLINK-6309) Memory consumer weights should be
calculated in job vertex level
[ https://issues.apache.org/jira/browse/FLINK-6309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15977892#comment-15977892 ]
Xu Pingyong commented on FLINK-6309:
------------------------------------
Memory consumer weights should be considered not only in terms of chaining , but also in slot sharing.
> Memory consumer weights should be calculated in job vertex level
> ----------------------------------------------------------------
>
> Key: FLINK-6309
> URL: https://issues.apache.org/jira/browse/FLINK-6309
> Project: Flink
> Issue Type: Improvement
> Components: Optimizer
> Reporter: Kurt Young
> Assignee: Xu Pingyong
>
> Currently in {{PlanFinalizer}}, we travel the whole job vertexes to calculate the memory consumer weights, and then assign the weights for each job vertex. In a case of a large job graph, e.g. with multiple joins, group reduces, the consumer weights will be high and the usable memory for each job vertex will be very low.
> I think it makes more sense to calculate the memory consumer weights in job vertex level (after chaining) to maximize the memory utility.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)