[jira] [Commented] (STORM-671) Measure tuple serialization/deserialization latency.

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot commented on STORM-671:
--------------------------------------

Github user revans2 commented on the pull request:

    https://github.com/apache/storm/pull/442#issuecomment-89333447
  
    @Lewuathe, I am really sorry that this took so long. Now that https://issues.apache.org/jira/browse/STORM-634 has gone in, the code does not merge cleanly.  The big difference is that now we are storing the metrics in thrift in zookeeper.  We also want to support rolling upgrades, so we need to make sure that the new metrics are optional in both the code, and in thrift.  If this is something that you just don't have time to finish I understand, and I'll try to come up with a patch at some point.


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