hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hong Tang (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-2037) Capturing interim progress times, CPU usage, and memory usage, when tasks reach certain progress thresholds
Date Tue, 07 Sep 2010 22:43:36 GMT

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

Hong Tang commented on MAPREDUCE-2037:
--------------------------------------

-1 on using EWMA to capture CPU usage. It is more useful to track the aggregated cpu tick
counter as raw data, and we can always calculate EWMA from that later, but not vice versa.
It'd be also useful to capture the number of threads that are included in the calculation.
So each entry looks like the following: <time, cpu-ticker-counter, #threads>. I'd also
like to capture CPU MHz number for the task tracker so that I can know if we are saturating
the CPU.

> Capturing interim progress times, CPU usage, and memory usage, when tasks reach certain
progress thresholds
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-2037
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2037
>             Project: Hadoop Map/Reduce
>          Issue Type: New Feature
>            Reporter: Dick King
>            Assignee: Dick King
>             Fix For: 0.22.0
>
>
> We would like to capture the following information at certain progress thresholds as
a task runs:
>    * Time taken so far
>    * CPU load [either at the time the data are taken, or exponentially smoothed]
>    * Memory load [also either at the time the data are taken, or exponentially smoothed]
> This would be taken at intervals that depend on the task progress plateaus.  For example,
reducers have three progress ranges -- [0-1/3], (1/3-2/3], and (2/3-3/3] -- where fundamentally
different activities happen.  Mappers have different boundaries, I understand, that are not
symmetrically placed.  Data capture boundaries should coincide with activity boundaries. 
For the state information capture [CPU and memory] we should average over the covered interval.
> This data would flow in with the heartbeats.  It would be placed in the job history as
part of the task attempt completion event, so it could be processed by rumen or some similar
tool and could drive a benchmark engine.

-- 
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