hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sangjin Lee (JIRA)" <j...@apache.org>
Subject [jira] [Created] (YARN-3741) consider nulling member maps/sets of TimelineEntity
Date Fri, 29 May 2015 05:27:17 GMT
Sangjin Lee created YARN-3741:
---------------------------------

             Summary: 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: Sangjin Lee


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.4#6332)

Mime
View raw message