hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4229) Intern counter names in the JT
Date Tue, 23 Oct 2012 21:36:14 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-4229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13482719#comment-13482719
] 

Hudson commented on MAPREDUCE-4229:
-----------------------------------

Integrated in Hadoop-trunk-Commit #2918 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/2918/])
    Updating credits for MAPREDUCE-4229. (Revision 1401493)

     Result = SUCCESS
daryn : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1401493
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt

                
> Intern counter names in the JT
> ------------------------------
>
>                 Key: MAPREDUCE-4229
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4229
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: jobtracker
>    Affects Versions: 1.0.2, 3.0.0, 2.0.2-alpha
>            Reporter: Todd Lipcon
>             Fix For: 3.0.0, 2.0.3-alpha, 0.23.5
>
>         Attachments: MAPREDUCE-4229-branch-0.23.patch, MAPREDUCE-4229-branch-0.23.patch,
MAPREDUCE-4229.patch, mr-4229.txt, MR-4229.txt
>
>
> In our experience, most of the memory in production JTs goes to storing counter names
(String objects and character arrays). Since most counter names are reused again and again,
it would be a big memory savings to keep a hash set of already-used counter names within a
job, and refer to the same object from all tasks.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message