[
https://issues.apache.org/jira/browse/AMBARI-12313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14617422#comment-14617422
]
Hudson commented on AMBARI-12313:
---------------------------------
ABORTED: Integrated in Ambari-branch-2.1 #179 (See
[https://builds.apache.org/job/Ambari-branch-2.1/179/])
AMBARI-12313. Service config pages load extremely slowly (especially on big
clusters). (atkach via yusaku) (yusaku:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ff5599e78a49c060be892718c2c3659dbd6ab4da)
* ambari-web/app/mappers/component_config_mapper.js
* ambari-web/app/utils/blueprint.js
* ambari-web/app/mixins/common/table_server_mixin.js
* ambari-web/test/utils/blueprint_test.js
> Service config pages load extremely slowly (especially on big clusters)
> -----------------------------------------------------------------------
>
> Key: AMBARI-12313
> URL: https://issues.apache.org/jira/browse/AMBARI-12313
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.1.0
> Reporter: Andrii Tkach
> Assignee: Andrii Tkach
> Priority: Critical
> Fix For: 2.1.0
>
> Attachments: AMBARI-12313.patch
>
>
> The following load time of the service config pages were observed on a 800+
> node cluster:
> HDFS: 36s
> MAPREDUCE2: 32s
> YARN: 35s
> HIVE: 32s
> HBASE: 30s
> Ambari Web makes a number of API calls, but majority of the time is spent on
> UI-side processing. We need to see what we can optimize.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
