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 "Kang Xiao (JIRA)" <ji...@apache.org> on 2011/02/21 06:09:44 UTC

[jira] Updated: (MAPREDUCE-2340) optimize JobInProgress.initTasks()

     [ https://issues.apache.org/jira/browse/MAPREDUCE-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kang Xiao updated MAPREDUCE-2340:
---------------------------------

    Attachment: MAPREDUCE-2340.patch

Patch attached.

A test for 1 job with 100000 maps  initialization on a 2400 nodes cluster is as follows:

original version:
initTasks() 17891 ms
createCache() 16090 ms 

opt version:
initTasks() 2243 ms
createCache() 326 ms


> optimize JobInProgress.initTasks()
> ----------------------------------
>
>                 Key: MAPREDUCE-2340
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2340
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: jobtracker
>    Affects Versions: 0.20.1, 0.21.0
>            Reporter: Kang Xiao
>         Attachments: MAPREDUCE-2340.patch
>
>
> JobTracker's hostnameToNodeMap cache can speed up JobInProgress.initTasks() and JobInProgress.createCache() significantly. A test for 1 job with 100000 maps on a 2400 cluster shows nearly 10 and 50 times speed up for initTasks() and createCache(). 

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira