[
https://issues.apache.org/jira/browse/MAPREDUCE-2855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13217807#comment-13217807
]
Hudson commented on MAPREDUCE-2855:
-----------------------------------
Integrated in Hadoop-Common-trunk-Commit #1791 (See
[https://builds.apache.org/job/Hadoop-Common-trunk-Commit/1791/])
MAPREDUCE-2855. Passing a cached class-loader to ResourceBundle creator to
minimize counter names lookup time. Contributed by Siddarth Seth. (Revision
1294436)
Result = SUCCESS
vinodkv :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1294436
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/util/ResourceBundles.java
> ResourceBundle lookup during counter name resolution takes a lot of time
> ------------------------------------------------------------------------
>
> Key: MAPREDUCE-2855
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2855
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 0.23.0
> Reporter: Todd Lipcon
> Assignee: Siddharth Seth
> Labels: mrv2
> Attachments: MR2855.txt
>
>
> 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
