Return-Path: X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BA11D911A for ; Mon, 4 Mar 2013 15:31:51 +0000 (UTC) Received: (qmail 42939 invoked by uid 500); 4 Mar 2013 15:31:51 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 42747 invoked by uid 500); 4 Mar 2013 15:31:50 -0000 Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-dev@incubator.apache.org Received: (qmail 42722 invoked by uid 99); 4 Mar 2013 15:31:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Mar 2013 15:31:49 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.128.181] (HELO mail-ve0-f181.google.com) (209.85.128.181) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Mar 2013 15:31:44 +0000 Received: by mail-ve0-f181.google.com with SMTP id d10so4812473vea.12 for ; Mon, 04 Mar 2013 07:31:21 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type:content-transfer-encoding :x-gm-message-state; bh=hjh5nxzWbbtBzYdK12UFXihswaCjkQmXDkM82s637M4=; b=mQ/RJ88qb/FHEBKg0oDlHp7qKko6Tm9jeGDsToJaj6bO7DmydEHnC7a5+YEHG5UOhO 20Z2zlP+YxVuxg/gceeBsR3Vvhf2k6WZDPFIClRVAsEC2WEexVizIf2duYF6JSqzOURC QbeFF+kyH85Ei/n5si6wX3rV+sX29jaOUTsI0Tnu5H4QiV8vpmriHNlI85Z8O2Gl0Zp1 F9N/EcJjli+7U+RTtfmXikqs8419fzSouPIQq0LDwLVKcDX85VMsK1dWXalcuHOD/ndd B0sor0pSuQx6lgHhtjhu2cPult24197FyHHdKZpJ0EZyaaSIMxdaDMff5acangj8okb3 bGEQ== X-Received: by 10.58.154.229 with SMTP id vr5mr8142911veb.11.1362411081858; Mon, 04 Mar 2013 07:31:21 -0800 (PST) MIME-Version: 1.0 Received: by 10.220.140.130 with HTTP; Mon, 4 Mar 2013 07:31:01 -0800 (PST) In-Reply-To: <97F4356AEA71904482CD192135C038F9011CC1D1335F@BANPMAILBOX01.citrite.net> References: <97F4356AEA71904482CD192135C038F9011CC1538672@BANPMAILBOX01.citrite.net> <97F4356AEA71904482CD192135C038F9011CC1D1335F@BANPMAILBOX01.citrite.net> From: David Nalley Date: Mon, 4 Mar 2013 10:31:01 -0500 Message-ID: Subject: Re: [ACS41][QA] Test plan for List API Performance Optimization To: cloudstack-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQkmtQEGBVBGHpp3HqrZWzxzfelRB3PpSNYD6/4HjaTKhLkgZHbtEL5Ogm8WXI/idcGozsO5 X-Virus-Checked: Checked by ClamAV on apache.org Inline reply. On Thu, Feb 28, 2013 at 2:09 AM, Sowmya Krishnan wrote: > Thanks for taking time to review the plan David. Answers inline. > >> -----Original Message----- >> From: David Nalley [mailto:david@gnsa.us] >> Sent: Thursday, February 28, 2013 3:26 AM >> To: cloudstack-dev@incubator.apache.org >> Subject: Re: [ACS41][QA] Test plan for List API Performance Optimization >> >> On Fri, Feb 22, 2013 at 1:24 PM, Sowmya Krishnan >> wrote: >> > Hi, >> > >> > I've posted a test plan for tracking the performance numbers for the >> > set of List APIs which were optimized as mentioned in >> > https://issues.apache.org/jira/browse/CLOUDSTACK-527 >> > Test plan is here: >> > https://cwiki.apache.org/confluence/display/CLOUDSTACK/List+API+Perfor >> > mance+Test+Plan >> > >> > Please take a look and post comments if any. >> > >> >> >> Thanks for writing this up, I have a couple of questions for you. >> >> I understand that you are running these tests and recording performance,= but it >> seems like you are measuring time. Is this time from query leaving the c= lient to >> answer? Is the client on the management server or not? >> > Yes. Time measured from the instant the query is fired from the client ti= ll the complete response has been received. Client is not in the management= server. I'll fire queries from a different server than MS or the DB. > >> I assume you are going to use the simulator, and not just have a populat= ed DB? >> (If that isn't the case, perhaps you can share the db >> dump.) >> > Plan is to use simulator to create Hosts, Routers, VMs etc... to generate= the load on DB and management server rather than populate DB. > Unless, at a later stage, there's a need to run much higher loads than wh= at I've mentioned in the test plan and if it's beyond what my test servers = can sustain... Then I might switch to using a DB dump. But I don't foresee = this for now. > >> Are you going to take a baseline from 4.0.{0,1}? >> > I have some numbers for List APIs pre-API optimization. I'll use those as= baseline. > >> Can this test be written up as a script and generate these statistics as= we get >> near a release to ensure we don't regress? >> > > Sure. I already have some scripts for generating load. I'll write few mor= e scripts to track time taken for List APIs. > Great - perhaps we can talk with Prasanna about getting those completely automated with jenkins. >> Are we assuming there will be no slow/long running queries? If there are= , it >> might be interesting to see what those are and if there are database iss= ues we >> can further work on? >> > I usually have the DB log slow queries. I can publish those too as part o= f the results. > >> What is 'failure' of this test? (slower than 4.0.x?, slower than n-perce= nt-faster >> than 4.0.x?) >> > I have some numbers recorded for few List APIs before the API re-factorin= g was done. I'll take those as baseline and call out failures based on that= for a start. Going forward, I'll try to automate the regressions so that w= e catch issues due to regressions if any. Can we get the baseline numbers published somewhere? (as well as the numbers you get in your tests of 4.1? --David