You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2012/08/18 21:31:39 UTC

[jira] [Commented] (MAPREDUCE-4565) Backport MR-2855 to branch-1: ResourceBundle lookup during counter name resolution takes a lot of time

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

Hadoop QA commented on MAPREDUCE-4565:
--------------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12541499/branch1-MR-4565.patch
  against trunk revision .

    -1 patch.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2749//console

This message is automatically generated.
                
> Backport MR-2855 to branch-1: ResourceBundle lookup during counter name resolution takes a lot of time
> ------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-4565
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4565
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>    Affects Versions: 1.0.3
>            Reporter: Karthik Kambatla
>            Assignee: Karthik Kambatla
>         Attachments: branch1-MR-4565.patch
>
>
> Loading a job status page in trunk takes a lot of time, and it seems like most of the time is spent resolving counter names. Looking through the JDK source, ResourceBundle.getBundle(String) ends up calling getClassContext() which is not very efficient. I think if we pass our own classloader manually it will be faster. In Counters.incrAllCounters, we may also be able to avoid setting the counter name if one is already set.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira