[
https://issues.apache.org/jira/browse/STORM-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14972350#comment-14972350
]
ASF GitHub Bot commented on STORM-1057:
---------------------------------------
Github user wangli1426 commented on the pull request:
https://github.com/apache/storm/pull/753#issuecomment-150751146
@d2r ,
Thank you very much for your prompt response. However, I cannot quite
understand your meaning by
> <cite>If the previous worker's throughput stats had declined sharply
before the worker had died, then weighting the current worker's throughput
stats still would be inaccurate, but in a different way. </cite>
I will appreciate it a lot if you could provide a concrete example.
I couldn't agree with you more than storm needs a History Server keep
historical information. Otherwise, executors are responsible for maintaining
their stats, which make them stateful. Is there any plan about the history
server?
By the way, adding throughput metric is my first step. And my ultimate goal
is to add ***normalized*** throughput, which leverages queueing theory to
provide a comparable performance metrics, similar but more accurate than
```capacity``` that is currently available in Storm. With normalized
throughput, one can easily identify the performance bottleneck of a running
topology by finding the executor with minimal number in normalized throughput.
With this capability, we can develop a runtime scheduling algorithm to make
better resource allocation. So what do you think?
> 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)
