[
https://issues.apache.org/jira/browse/STORM-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14339019#comment-14339019
]
ASF GitHub Bot commented on STORM-671:
--------------------------------------
Github user revans2 commented on a diff in the pull request:
https://github.com/apache/storm/pull/442#discussion_r25457668
--- Diff: storm-core/src/clj/backtype/storm/stats.clj ---
@@ -235,6 +237,11 @@
(let [key [component stream]]
(update-executor-stat! stats :failed key (stats-rate stats))))
+(defn bolt-deserialize-time!
+ [^BoltExecutorStats stats component stream deserialize-time]
--- End diff --
I am nervious about this being specific to a bolt, and the spout calling
into this. Clojure is going to have to use reflection to make this work, which
is slow.
> 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)
