[
https://issues.apache.org/jira/browse/STORM-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14395832#comment-14395832
]
ASF GitHub Bot commented on STORM-671:
--------------------------------------
Github user Parth-Brahmbhatt commented on the pull request:
https://github.com/apache/storm/pull/442#issuecomment-89620855
@Lewuathe The metrics is already stored in zookeeper what you need to do is
ensure the thrift structure has serialization metric as an additional field
(point 2) and change the converter
https://github.com/apache/storm/blob/master/storm-core/src/clj/backtype/storm/stats.clj#L369
to handle conversion from the clojure metric to thrift metrics and vice versa.
Let me know if I can help in anyway.
> Measure tuple serialization/deserialization latency.
> ----------------------------------------------------
>
> Key: STORM-671
> URL: https://issues.apache.org/jira/browse/STORM-671
> Project: Apache Storm
> Issue Type: New Feature
> Reporter: Robert Joseph Evans
> Assignee: Kai Sasaki
>
> Some times the serialization/deserialization cost can be very high, and it is
> not currently measured anywhere in storm. We should measure it, at least in
> a similar way to how we do execute and process latency.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
