hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luke Lu (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6919) Metrics2: metrics framework
Date Thu, 16 Sep 2010 00:22:34 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-6919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12909964#action_12909964
] 

Luke Lu commented on HADOOP-6919:
---------------------------------

Summary of changes (framework only) vs the jumbo patch for yahoo 0.20.104 (attached in HADOOP-6728
for common/hdfs/mapreduce):

* Extracted metadata (name and description) for each metric/tag to an interned info object,
resulting 33% memory saving per metric/tag (16 bytes vs 24 bytes per metric update (on 64-bit
platform) in previous patch (which has the same overhead in the old framework which doesn't
even have metric description available.)
* Simplified metrics source creation with @Metrics (for class) and @Metric (for method and
field) annotations (see the metrics2 package doc (package-info.java) and the [design doc|http://wiki.apache.org/hadoop/HADOOP-6728-MetricsV2]
for examples.)

> Metrics2: metrics framework
> ---------------------------
>
>                 Key: HADOOP-6919
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6919
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: metrics
>    Affects Versions: 0.20.2
>            Reporter: Luke Lu
>            Assignee: Luke Lu
>             Fix For: 0.22.0
>
>         Attachments: hadoop-6919-trunk-v1.patch
>
>
> The jira tracks the new metrics framework only changes, i.e., it doesn't track the instrumentation
changes (and compatibility issues) to existing code.

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