[ http://issues.apache.org/jira/browse/HADOOP-237?page=comments#action_12420695 ]
Milind Bhandarkar commented on HADOOP-237: ------------------------------------------ But then, mapIO needs to be called everytime eiither numBytesInput or numBytesOutput change (they change in different places). So, I don't see a performance difference. Maybe having a different record for each metric is a better solution performance wise, because it will avoid the record-copy overhead, but then it will increase record update overhead, by sending two separate packets. > Standard set of Performance Metrics for Hadoop > ---------------------------------------------- > > Key: HADOOP-237 > URL: http://issues.apache.org/jira/browse/HADOOP-237 > Project: Hadoop > Type: Improvement > Components: metrics > Versions: 0.3.0 > Environment: All > Reporter: Milind Bhandarkar > Assignee: Milind Bhandarkar > Attachments: hadoop-metrics.patch > > I am starting to use Hadoop's shiny new Metrics API to publish performance > (and other) Metrics of running jobs and other daemons. > Which performance metrics are people interested in seeing ? If possible, > please group them according to modules, such as map-reduce, dfs, > general-cluster-related etc. I will follow this process: > 1. collect this list > 2. assess feasibility of obtaining metric > 3. assign context/record/metrics names > 4. seek approval for names > 5. instrument the code. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
