ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrii Tkach (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-12760) FE: Add experimental flag to show "page loaded in X seconds" on important pages
Date Thu, 13 Aug 2015 17:01:45 GMT

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

Andrii Tkach commented on AMBARI-12760:
---------------------------------------

committed to trunk and branch-2.1

> FE: Add experimental flag to show "page loaded in X seconds" on important pages
> -------------------------------------------------------------------------------
>
>                 Key: AMBARI-12760
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12760
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-web
>    Affects Versions: 2.1.2
>            Reporter: Andrii Tkach
>            Assignee: Andrii Tkach
>             Fix For: 2.1.2
>
>         Attachments: AMBARI-12760.patch
>
>
> To make it easy to determine how long it takes to render a page, we need a message at
the bottom of important pages which says "Page loaded in X seconds and Y milliseconds". This
will be useful for anyone to accurately measure UI perf issues.
> "Loading" unfortunately means different things on different pages.
> * Dashboard
> ** Metrics: All tiles show and page is available for interaction. Data in tiles need
not be loaded.
> ** Heatmaps: Heatmap data should be shown for appropriate hosts.
> ** Config History: Table is available for interaction.
> * Service
> ** Summary: Page is available for interaction. Data in graphs need not be loaded.
> ** Heatmaps: Heatmap data should be shown for appropriate hosts.
> ** Configs: Config fields should be available for interaction. Should update when config-groups
are selected.
> * Hosts
> ** Time taken to populate hosts table and make it available. This should keep updating
when various filters and sorts are used.
> * Alerts
> ** Time taken to populate table and make it available. This should keep updating when
various filters and sorts are used.
> The mechanism should be a mixin that any page can use with ease if needed. Ideally, we
want this hooked into Ember rendering pipeline so that the numbers include the time taken
to render the view. Hooking to mapper end time is *not* accurate. 
> We can call the experimental flag "showPageLoadTime". 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message