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 "Arun Suresh (JIRA)" <ji...@apache.org> on 2017/03/31 00:09:41 UTC
[jira] [Commented] (YARN-6418) Reduce Resource object creation and
overhead in Capacity scheduler inner loop
[ https://issues.apache.org/jira/browse/YARN-6418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15950091#comment-15950091 ]
Arun Suresh commented on YARN-6418:
-----------------------------------
[~leftnoteasy], given the work done on YARN-6040. I understand you had performed some profiling on the scheduler and identified a couple of places you found the PBImpl object instantiation was getting a bit expensive, so would be interested in your thoughts here as well.
> Reduce Resource object creation and overhead in Capacity scheduler inner loop
> -----------------------------------------------------------------------------
>
> Key: YARN-6418
> URL: https://issues.apache.org/jira/browse/YARN-6418
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: capacityscheduler, resourcemanager
> Affects Versions: 2.7.3, 3.0.0-alpha2, 2.8
> Reporter: Roni Burd
> Assignee: Roni Burd
>
> Resource object is used multiple due to ResourceCalculator creates new instances on every method call. This gets called several times on each node HB. Resource is a very expensive object that relies on Protobufs
> The change is to remove the need to use protobuf on the Resource object and avoid creating many objects in the Resource Calculator all the time
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org