hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joep Rottinghuis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4710) Add peak memory usage counter for each task
Date Sat, 09 Nov 2013 05:27:18 GMT

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

Joep Rottinghuis commented on MAPREDUCE-4710:
---------------------------------------------

Cindy, is your experience that your JVM is giving memory back to the OS to make PHYSICAL_MEMORY_BYTES_MAX
inaccurate ?

What is the sampling rate to use to detect the max, or is sampling not needed here ?




> Add peak memory usage counter for each task
> -------------------------------------------
>
>                 Key: MAPREDUCE-4710
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4710
>             Project: Hadoop Map/Reduce
>          Issue Type: New Feature
>          Components: task
>    Affects Versions: 1.0.2
>            Reporter: Cindy Li
>            Assignee: Cindy Li
>            Priority: Minor
>              Labels: patch
>         Attachments: MAPREDUCE-4710-trunk.patch, mapreduce-4710-v1.0.2.patch, mapreduce-4710.patch,
mapreduce4710.patch
>
>
> Each task has counters PHYSICAL_MEMORY_BYTES and VIRTUAL_MEMORY_BYTES, which are snapshots
of memory usage of that task. They are not sufficient for users to understand peak memory
usage by that task, e.g. in order to diagnose task failures, tune job parameters or change
application design. This new feature will add two more counters for each task: PHYSICAL_MEMORY_BYTES_MAX
and VIRTUAL_MEMORY_BYTES_MAX. 



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message