You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "He Tianyi (JIRA)" <ji...@apache.org> on 2016/08/12 04:03:20 UTC
[jira] [Assigned] (YARN-5510) Optimize Resource implementation for
instantiation
[ https://issues.apache.org/jira/browse/YARN-5510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
He Tianyi reassigned YARN-5510:
-------------------------------
Assignee: He Tianyi
> Optimize Resource implementation for instantiation
> --------------------------------------------------
>
> Key: YARN-5510
> URL: https://issues.apache.org/jira/browse/YARN-5510
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Affects Versions: 2.6.0
> Reporter: He Tianyi
> Assignee: He Tianyi
>
> According to YARN-5479, many {{Resource}} instances are created as intermediate result of calculating in scheduler (as a result of {{Resources.subtract}} and {{Resources.add}}). This introduces pressure on garbage collector as well as CPU cycles for scheduling.
> Therefore, the issue proposes a lightweight implementation of {{Resource}}, which optimized for scheduler usage. That is, making instantiation of {{Resource}} cheaper.
> In discussion of {{YARN-5479}}, we thought maybe sticking to one version of implementation avoids unnecessary complexity.
> In current implementation {{ResourceImplPB}}, a builder is also created during construction. Also, {{maybeInitBuilder}} get called during each {{setMemory}} or {{setVirtualCores}}. The {{builder}} get prepared regardless whether {{Resource}} will be exchanged via IPC or not.
> However, in scheduler (which performance is critical), most of these instances are just intermediate result and not exposed.
> Suppose we could move builder related code into {{getProto}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org