[jira] [Updated] (YARN-6339) Improve performance for createAndGetApplicationReport

["yunjiong zhao (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/YARN-6339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

yunjiong zhao updated YARN-6339:
--------------------------------
    Attachment: YARN-6339.001.patch

This patch have 3 improvements:
1. Use substring instead of replace
2. Update logAggregationStatusForAppReport to reduce time spend in getLogAggregationStatusForAppReport.
3. Inside getLogAggregationReportsForApp, move somecondition checks from for loop to outside, so for some applications, it won't run that for loop.


> Improve performance for createAndGetApplicationReport
> -----------------------------------------------------
>
>                 Key: YARN-6339
>                 URL: https://issues.apache.org/jira/browse/YARN-6339
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: yunjiong zhao
>            Assignee: yunjiong zhao
>         Attachments: YARN-6339.001.patch
>
>
> There are two performance issue when calling createAndGetApplicationReport:
> One is inside ProtoUtils.convertFromProtoFormat, replace is too slow for clusters which have more than 3000 nodes. Use substring is much better: https://issues.apache.org/jira/browse/YARN-6285?focusedCommentId=15923241&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15923241
> Another one is inside getLogAggregationReportsForApp, if some application's LogAggregationStatus is TIME_OUT, every time it was called it will create an HashMap which will produce lots of garbage.



--
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