tez-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Seth (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (TEZ-376) Reduce Processor can parallelize I/O/Processor initialization
Date Tue, 20 Aug 2013 05:30:53 GMT

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

Siddharth Seth updated TEZ-376:

    Status: Patch Available  (was: Open)

Re-submitting. Cancelled the patch earlier since I was seing some task failures after applying
this patch. Narrowed that down to TEZ-379. This is ready for review.
> Reduce Processor can parallelize I/O/Processor initialization
> -------------------------------------------------------------
>                 Key: TEZ-376
>                 URL: https://issues.apache.org/jira/browse/TEZ-376
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Siddharth Seth
>            Assignee: Siddharth Seth
>              Labels: TEZ-0.2.0
>         Attachments: TEZ-376.2.txt, TEZ-376.txt
> Reported by [~gopalv]. Reduce initialization can take a fair amount of time after shuffle
is complete - depending on how expensive the Reduce initialization is.
> Quote from Gopal's investigation
> 1.6 seconds is spent in ReflectionUtils.newInstance() -> ReflectionUtils.setConf()
of which 1.2 seconds is Utilities.getMapRedWork().

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

View raw message