Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ambari-dev@incubator.apache.org
Date: Thu, 17 Oct 2013 21:34:46 +0000 (UTC)
From: "Mahadev konar (JIRA)" <jira@apache.org>
To: ambari-dev@incubator.apache.org
Message-ID: <JIRA.12665281.1377282003035.83013.1382045686088@arcas>
In-Reply-To: <JIRA.12665281.1377282003035@arcas>
References: <JIRA.12665281.1377282003035@arcas>
Subject: [jira] [Updated] (AMBARI-3015) Ambari API latency increases
 linearly to load
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AMBARI-3015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mahadev konar updated AMBARI-3015:
----------------------------------

    Fix Version/s:     (was: 1.4.0)
                   1.4.2
         Assignee:     (was: Mahadev konar)

> Ambari API latency increases linearly to load
> ---------------------------------------------
>
>                 Key: AMBARI-3015
>                 URL: https://issues.apache.org/jira/browse/AMBARI-3015
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 1.4.0
>            Reporter: Srimanth Gunturi
>              Labels: performance
>             Fix For: 1.4.2
>
>         Attachments: 1Thread.png, 2Threads.png, 3Threads.png
>
>
> Setup: In a thread I am calling Ambari UI's 5 most used APIs. They are:
> {noformat}
> /api/v1/clusters/${cluster}/hosts?fields=Hosts/host_name,Hosts/public_host_name,Hosts/disk_info,Hosts/cpu_count,Hosts/total_mem,Hosts/host_status,Hosts/last_heartbeat_time,Hosts/os_arch,Hosts/os_type,Hosts/ip,host_components,metrics/disk,metrics/load/load_one
> {noformat}
> {noformat}
> /api/v1/clusters/${cluster}/services?fields=components/ServiceComponentInfo,components/host_components,components/host_components/HostRoles,components/host_components/metrics/jvm/memHeapUsedM,components/host_components/metrics/jvm/memHeapCommittedM,components/host_components/metrics/mapred/jobtracker/trackers_decommissioned,components/host_components/metrics/cpu/cpu_wio,components/host_components/metrics/rpc/RpcQueueTime_avg_time,components/host_components/metrics/flume/flume,components/host_components/metrics/yarn/Queue
> {noformat}
> {noformat}
> /api/v1/clusters/vm/requests?to=end&page_size=10&fields=*,tasks/Tasks/*
> {noformat}
> {noformat}
> /api/v1/clusters/vm/host_components?fields=HostRoles/nagios_alerts&HostRoles/component_name=NAGIOS_SERVER
> {noformat}
> {noformat}
> /api/v1/clusters/vm/services?fields=ServiceInfo,components/host_components/HostRoles/desired_state,components/host_components/HostRoles/state
> {noformat}
> The above I call one after the other and loop 100 times.
> When I run 2 threads in parallel, it takes twice as long as 1 thread. 
> When I run 3 threads in parallel, it takes thrice as long as 1 thread.
> It looks like each sessions requests are done one after the other in serial.
> Images attached. 


--
This message was sent by Atlassian JIRA
(v6.1#6144)