[
https://issues.apache.org/jira/browse/STORM-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14493488#comment-14493488
]
ASF GitHub Bot commented on STORM-671:
--------------------------------------
Github user nathanmarz commented on the pull request:
https://github.com/apache/storm/pull/442#issuecomment-92574396
-1
I can't +1 this until some data is shown showing the performance impact of
this. I suspect this metric may need to be sampled just like the other metrics
to prevent it from having a bad impact on performance.
> 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)
