You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@storm.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/01/12 22:13:40 UTC

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

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

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

Github user asfgit closed the pull request at:

    https://github.com/apache/storm/pull/442


> Measure tuple serialization/deserialization latency.
> ----------------------------------------------------
>
>                 Key: STORM-671
>                 URL: https://issues.apache.org/jira/browse/STORM-671
>             Project: Apache Storm
>          Issue Type: New Feature
>          Components: storm-core
>            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)