[
https://issues.apache.org/jira/browse/STORM-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14336312#comment-14336312
]
ASF GitHub Bot commented on STORM-671:
--------------------------------------
GitHub user Lewuathe opened a pull request:
https://github.com/apache/storm/pull/442
[STORM-671] Measure tuple serialization/deserialization latency.
Measure deserialization time in spout and bolt.
These values can be see on dashboard UI.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Lewuathe/storm deserialization-time
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/442.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #442
----
commit f5bc66f32b8bbb4d770ebb245ba6590d97ff2c1d
Author: lewuathe <[email protected]>
Date: 2015-02-25T10:02:32Z
[STORM-671] Measure tuple serialization/deserialization latency.
----
> 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)
