[ https://issues.apache.org/jira/browse/YARN-3741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15922940#comment-15922940 ]
Haibo Chen commented on YARN-3741: ---------------------------------- [~sjlee0] Can I take this one up? > consider nulling member maps/sets of TimelineEntity > --------------------------------------------------- > > Key: YARN-3741 > URL: https://issues.apache.org/jira/browse/YARN-3741 > Project: Hadoop YARN > Issue Type: Sub-task > Components: timelineserver > Affects Versions: YARN-2928 > Reporter: Sangjin Lee > Assignee: Vrushali C > Labels: YARN-5355 > > Currently there are multiple collection members of TimelineEntity that are > always instantiated, regardless of whether they are used or not: info, > configs, metrics, events, isRelatedToEntities, and relatesToEntities. > Since TimelineEntities will be created very often and in lots of cases many > of these members will be empty, creating these empty collections is wasteful > in terms of garbage collector pressure. > It would be good to start out with null members, and instantiate these > collections only if they are actually used. Of course, we need to make that > contract very clear and refactor all client code to handle that scenario. -- This message was sent by Atlassian JIRA (v6.3.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org