hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dhruba borthakur (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-2124) Add job counters for measuring time spent in three different phases in reducers
Date Mon, 11 Oct 2010 18:27:34 GMT

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

dhruba borthakur commented on MAPREDUCE-2124:
---------------------------------------------

> The cost of additional framework counters in the JobTracker is pretty high

are you worried about memory or CPU?  Doesn't one job-counter require only one object per
job?

> Add job counters for measuring time spent in three different phases in reducers
> -------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-2124
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2124
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: jobtracker
>    Affects Versions: 0.22.0
>            Reporter: Scott Chen
>            Assignee: Scott Chen
>            Priority: Minor
>             Fix For: 0.22.0
>
>
> We currently have SLOTS_MILLIS_REDUCES which measures the total slot time of reducer.
> It will be useful if we have
> {code}
> SLOTS_MILLIS_REDUCES_COPY
> SLOTS_MILLIS_REDUCES_SORT
> SLOTS_MILLIS_REDUCES_REDUCE
> {code}
> which measures three different phases of a reducer.
> This will help us identify the bottleneck of the reducers.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message