[
https://issues.apache.org/jira/browse/STORM-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14938881#comment-14938881
]
ASF GitHub Bot commented on STORM-1057:
---------------------------------------
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/753#issuecomment-144543081
Actually I thought about this a bit more and I am not sure what value this
adds over dividing the emitted counts that we already have by the time window
that they are for. I don't see a reason to add in more code to get a number we
already know. I am -1 for this approach. I am fine with doing the calculation
for the rate and displaying it in the UI. That would be helpful, but I don't
see a reason to try and collect it again, in a different way.
> 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)
