Return-Path: X-Original-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9348510605 for ; Thu, 1 Aug 2013 09:19:39 +0000 (UTC) Received: (qmail 97813 invoked by uid 500); 1 Aug 2013 09:19:34 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 97597 invoked by uid 500); 1 Aug 2013 09:19:33 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 97589 invoked by uid 99); 1 Aug 2013 09:19:33 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Aug 2013 09:19:33 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of write2kishore@gmail.com designates 209.85.219.49 as permitted sender) Received: from [209.85.219.49] (HELO mail-oa0-f49.google.com) (209.85.219.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Aug 2013 09:19:28 +0000 Received: by mail-oa0-f49.google.com with SMTP id n10so1389228oag.8 for ; Thu, 01 Aug 2013 02:19:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=mBN+UU4qiyJuvwE5GAkDLDTui6BLOUAtE4EKe02F5HM=; b=leDU2mRKY/TJWflOk6ULPkIiVVkZ6etuex6PwnUupI8acAfXr20hWH81FJLcVYj/pd h8GHHkxZXmwLrFxkaPB16D5v1wqak0s+ayH+1KIoG45QV9gk6KThEQ4ngvmUmyQ3eda+ CUcBY/2oOFLj2LrVeHF7odhtClvCA5SmY31a81W3erGso0ETIAjwMbnp1HswZVwlJZj/ 7wyZFehC80HbUeNXmWLaxC8qfbugBregiQyekRdWxTQSR9bESBvFVS9VtAQhQSUAd5/I chRXLhWDnB2qvpXqX+6r60ux0TZwuKUOwLq8NeelTwKEnyeNMYdhtbU5iBDIWS1DCMMi Ay7Q== MIME-Version: 1.0 X-Received: by 10.50.82.104 with SMTP id h8mr84510igy.17.1375348747511; Thu, 01 Aug 2013 02:19:07 -0700 (PDT) Received: by 10.42.66.13 with HTTP; Thu, 1 Aug 2013 02:19:07 -0700 (PDT) In-Reply-To: References: Date: Thu, 1 Aug 2013 14:49:07 +0530 Message-ID: Subject: Re: Extra start-up overhead with hadoop-2.1.0-beta From: Krishna Kishore Bonagiri To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=e89a8f503b1689ad6c04e2df559e X-Virus-Checked: Checked by ClamAV on apache.org --e89a8f503b1689ad6c04e2df559e Content-Type: text/plain; charset=ISO-8859-1 Hi, Please share with me if you anyone has an answer or clues to my question regarding the start up performance. Also, one more thing I have observed today is the time taken to run a command on a container went up by more than a second in this latest version. When using 2.0.4-alpha, it used to take 0.3 to 0.5 seconds from the point I call startContainer() to the point the command is started on the container. where as When using 2.1.0-beta, it is taking around 1.5 seconds from the point it came to the call back onContainerStarted() to the point the command is seen started running on the container. Thanks, Kishore On Thu, Jul 25, 2013 at 8:38 PM, Krishna Kishore Bonagiri < write2kishore@gmail.com> wrote: > Hi, > > I have been using the hadoop-2.0.1-beta release candidate and observed > that it is slower in running my simple application that runs on 2 > containers. I have tried to find out which parts of it is really having > this extra overhead(compared to hadoop-2.0.4-alpha), and here is what I > found that. > > 1) From the point my Client has submitted the Application Master to RM, it > is taking 2 seconds extra > 2) From the point my container request are set up by Application Master, > till the containers are allocated, it is taking 2 seconds extra > > Is this overhead expected with the changes that went into the new version? > Or is there to improve it by changing something in configurations or so? > > Thanks, > Kishore > --e89a8f503b1689ad6c04e2df559e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,
=A0 Please share with me if you anyone has an answ= er or clues to my question regarding the start up performance.=A0

Also, one more thing I have observed today is the time take= n to run a command on a container went up by more than a second in this lat= est version.

When using 2.0.4-alpha, it used to take 0.3 to 0.5 seco= nds from the point I call startContainer() to the =A0point the command is s= tarted on the container.

where as

When using 2.1.0-beta, it is taking around 1.5 seconds from the = point it came to the call back=A0onContainerStarted() to the point the comm= and is seen started running on the container.

Than= ks,
Kishore


On Thu, Jul 25, 2013 at 8:38 PM, Krishna Kishore Bonagiri = <write2kishore@gmail.com> wrote:
Hi,

=A0 I have= been using the hadoop-2.0.1-beta release candidate and observed that it is= slower in running my simple application that runs on 2 containers. I have = tried to find out which parts of it is really having this extra overhead(co= mpared to hadoop-2.0.4-alpha), and here is what I found that.

1) From the point my Client has submitted the Applicati= on Master to RM, it is taking 2 =A0seconds extra
2) From the poin= t my container request are set up by Application Master, till the container= s are allocated, it is taking 2 seconds extra

Is this overhead expected with the changes that went in= to the new version? Or is there to improve it by changing something in conf= igurations or so?

Thanks,
Kishore

--e89a8f503b1689ad6c04e2df559e--