[jira] [Commented] (STORM-820) UI Topology & Component Pages have long load times with large, highly-connected Topologies

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/STORM-820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14942313#comment-14942313 ] 

ASF GitHub Bot commented on STORM-820:
--------------------------------------

Github user revans2 commented on the pull request:

    https://github.com/apache/storm/pull/554#issuecomment-145251891
  
    @d2r please upmerge.  The code still looks great but it looks like upSecs and a debug were added into the results.  I really want to get this in, as it will speed up page loads a lot.


> 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)