[
https://issues.apache.org/jira/browse/STORM-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15037971#comment-15037971
]
ASF GitHub Bot commented on STORM-1057:
---------------------------------------
Github user unsleepy22 commented on a diff in the pull request:
https://github.com/apache/storm/pull/753#discussion_r46569121
--- Diff: storm-core/src/clj/backtype/storm/daemon/executor.clj ---
@@ -339,7 +341,7 @@
(if (seq data-points)
(task/send-unanchored task-data Constants/METRICS_STREAM_ID
[task-info data-points] overflow-buffer))))
([executor-data task-data ^TupleImpl tuple]
- (metrics-tick executor-data task-data tuple nil)
+ (metrics-tick executor-data task-data tuple nil)
--- End diff --
indent by 1 space
> Add throughput metric to spout/bolt and display them on web ui
> --------------------------------------------------------------
>
> Key: STORM-1057
> URL: https://issues.apache.org/jira/browse/STORM-1057
> Project: Apache Storm
> Issue Type: New Feature
> Components: storm-core
> Reporter: Li Wang
> Assignee: Li Wang
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> Throughput is a fundamental metric to reasoning about the performance
> bottleneck of a topology. Displaying the throughputs of components and tasks
> on the web ui could greatly facilitate the user identifying the performance
> bottleneck and checking whether the the workload among components and tasks
> are balanced.
> What to do:
> 1. Measure the throughput of each spout/bolt.
> 2. Display the throughput metrics on web UI.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
