[
https://issues.apache.org/jira/browse/STORM-820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731086#comment-14731086
]
ASF GitHub Bot commented on STORM-820:
--------------------------------------
Github user d2r commented on the pull request:
https://github.com/apache/storm/pull/554#issuecomment-137796743
Leaving a comment here for now: the key
[here](https://github.com/d2r/storm/blob/6b606cf68f60858bdc9064c1fe50c873e6dd1971/storm-core/src/clj/backtype/storm/stats.clj#L961)
should be `:complete-latency` or else each spout's complete latency will show
0.000 on the topology page. (Component page is not affected.)
> UI Topology & Component Pages have long load times with large,
> highly-connected Topologies
> ------------------------------------------------------------------------------------------
>
> Key: STORM-820
> URL: https://issues.apache.org/jira/browse/STORM-820
> Project: Apache Storm
> Issue Type: Improvement
> Affects Versions: 0.11.0
> Reporter: Derek Dagit
> Assignee: Derek Dagit
>
> In the UI, the Topology Page and the Component Page each make a
> getTopologyInfoWithOpts thrift call to nimbus for executor heartbeat data.
> Metrics from this data are then aggregated in by the UI daemon for display.
> When large topologies, with high-connectedness, are viewed in this way, the
> load times for each page can be minutes long. In addition, heap usage by the
> nimbus JVM can grow substantially as data for each executor, component, &
> stream is serialized to be sent to the UI.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
