[
https://issues.apache.org/jira/browse/YARN-6245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15955811#comment-15955811
]
Wangda Tan commented on YARN-6245:
----------------------------------
[~roniburd], for patch submission, I agree with [~kasha] to submit one patch to
this one and close YARN-6418 as dup. Please feel free to take over this JIRA
since I may not have bandwidth to work on it in short term.
For approach suggested by [~kasha], I'm a little afraid it adds too much
effort. For example, we need to clearly identify which "resource" references in
scheduler need to be PBImpl, etc. And Resources/ResourceCalculator classes are
used outside of YARN as well. Updating all of them to use LightResource might
be problematic. I'm fine if effort of the approach is not too much.
> Add FinalResource object to reduce overhead of Resource class instancing
> ------------------------------------------------------------------------
>
> Key: YARN-6245
> URL: https://issues.apache.org/jira/browse/YARN-6245
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Wangda Tan
> Attachments: observable-resource.patch,
> YARN-6245.preliminary-staled.1.patch
>
>
> There're lots of Resource object creation in YARN Scheduler, since Resource
> object is backed by protobuf, creation of such objects is expensive and
> becomes bottleneck.
> To address the problem, we can introduce a FinalResource (Is it better to
> call it ImmutableResource?) object, which is not backed by PBImpl. We can use
> this object in frequent invoke paths in the scheduler.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
