[
https://issues.apache.org/jira/browse/STORM-820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14546899#comment-14546899
]
ASF GitHub Bot commented on STORM-820:
--------------------------------------
GitHub user d2r opened a pull request:
https://github.com/apache/storm/pull/554
[STORM-820] Aggregate topo stats on nimbus, not ui
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/d2r/storm storm-820-agg-stats-on-nimbus
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/554.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #554
----
commit 3d3c2b7701e351d63b8757155a3e37ec84f497b2
Author: Derek Dagit <[email protected]>
Date: 2015-05-13T13:35:23Z
Aggregate topo stats on nimbus, not ui
----
> 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)
