Return-Path: X-Original-To: apmail-hadoop-common-user-archive@www.apache.org Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 750851074E for ; Mon, 21 Oct 2013 15:54:45 +0000 (UTC) Received: (qmail 90407 invoked by uid 500); 21 Oct 2013 15:54:38 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 90090 invoked by uid 500); 21 Oct 2013 15:54:38 -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 90081 invoked by uid 99); 21 Oct 2013 15:54:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Oct 2013 15:54:37 +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 tucu@cloudera.com designates 209.85.128.42 as permitted sender) Received: from [209.85.128.42] (HELO mail-qe0-f42.google.com) (209.85.128.42) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Oct 2013 15:54:33 +0000 Received: by mail-qe0-f42.google.com with SMTP id gc15so3934497qeb.29 for ; Mon, 21 Oct 2013 08:54:10 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=HwKnlp92XYcErFDGK77KOpn6ayaFvM+bva4d0s1z3bg=; b=i1jhf2pPhDoSFFqQKxyxBXZxbsERf538vhCZ2S+hi+Y8oAqudT+6Rm3N+b2nK6IL1O 7F8JyWKDzK2v2A46T4jsuYoLWORoz2fuxC4St011H0n/kQ9tWsTV45ZVDd0SWrYwTvkC wpiPaRaA7gaObqaRJXQW618/9VTsGvHp7NhNza9nLNE9/IgeqUFZ42vcp41Am62cGGmJ 6fCI/UKDWcFA26X29/LkmvALksaYL+IaEObQn6HXbtYuadrgBVr9P91GwDKrsmO3AOvz g/VfYwI8fD9SmPAt6k8p1Os12V7qN7acYDWS8n5rpZ5dzXTcDt7zY0BzWb7qkVkauyxj dryw== X-Gm-Message-State: ALoCoQk3CoSEevRM4axCsnn4qnNJ9BZeUwyixYnslmCzuhj6KAjmqy2D7FM3axE/0vKDTqoZnNdT X-Received: by 10.224.12.207 with SMTP id y15mr3095503qay.101.1382370850124; Mon, 21 Oct 2013 08:54:10 -0700 (PDT) MIME-Version: 1.0 Received: by 10.96.69.228 with HTTP; Mon, 21 Oct 2013 08:53:38 -0700 (PDT) In-Reply-To: References: From: Alejandro Abdelnur Date: Mon, 21 Oct 2013 08:53:38 -0700 Message-ID: Subject: Re: Time taken for starting AMRMClientAsync To: "common-user@hadoop.apache.org" Content-Type: multipart/alternative; boundary=089e0149cf967842b504e9424b51 X-Virus-Checked: Checked by ClamAV on apache.org --089e0149cf967842b504e9424b51 Content-Type: text/plain; charset=ISO-8859-1 Hi Krishna, Those 900ms seems consistent with the numbers we found while doing some benchmarks in the context of Llama: http://cloudera.github.io/llama/ "We found that the first application master created from a client process takes around 900 ms to be ready to submit resource requests. Subsequent application masters created from the same client process take a mean of 20 ms. The application master submission throughput (discarding the first submission) tops at approximately 100 application masters per second." I believe there is room for improvement there. Cheers On Mon, Oct 21, 2013 at 7:16 AM, Krishna Kishore Bonagiri < write2kishore@gmail.com> wrote: > Hi, > I am seeing the following call to start() on AMRMClientAsync taking from > 0.9 to 1 second. Why does it take that long? Is there a way to reduce it, I > mean does it depend on any of the interval parameters or so in > configuration files? I have tried reducing the value of the first argument > below from 1000 to 100 seconds also, but that doesn't help. > > AMRMClientAsync.CallbackHandler allocListener = new > RMCallbackHandler(); > amRMClient = AMRMClientAsync.createAMRMClientAsync(1000, > allocListener); > amRMClient.init(conf); > amRMClient.start(); > > > Thanks, > Kishore > > -- Alejandro --089e0149cf967842b504e9424b51 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi Krishna,

Those 900ms seems consisten= t with the numbers we =A0found while doing some benchmarks in the context o= f Llama:


"= We found that the first application master created from a client process ta= kes around 900 ms to be ready to submit resource requests. Subsequent appli= cation masters created from the same client process take a mean of 20 ms. T= he application master submission throughput (discarding the first submissio= n) tops at approximately 100 application masters per second."

I believe there is room for imp= rovement there.

Cheers


On Mon,= Oct 21, 2013 at 7:16 AM, Krishna Kishore Bonagiri <write2kishore@gm= ail.com> wrote:
Hi,
=A0 I am seeing the= following call to start() on AMRMClientAsync taking from 0.9 to 1 second. = Why does it take that long? Is there a way to reduce it, I mean does it dep= end on any of the interval parameters or so in configuration files? I have = tried reducing the value of the first argument below from 1000 to 100 secon= ds also, but that doesn't help.

=A0 =A0 AMRMClientAsync.CallbackHandler allocListe= ner =3D new RMCallbackHandler();
=A0 =A0 amRMClient =3D AMRMClien= tAsync.createAMRMClientAsync(1000, allocListener);
=A0 =A0 amRMCl= ient.init(conf);
=A0 =A0 amRMClient.start();


<= div>Thanks,
Kishore




--
Alejandro --089e0149cf967842b504e9424b51--