Return-Path: Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: (qmail 73944 invoked from network); 11 Apr 2011 07:30:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 11 Apr 2011 07:30:28 -0000 Received: (qmail 83739 invoked by uid 500); 11 Apr 2011 07:30:25 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 83662 invoked by uid 500); 11 Apr 2011 07:30:22 -0000 Mailing-List: contact common-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-user@hadoop.apache.org Delivered-To: mailing list common-user@hadoop.apache.org Received: (qmail 83654 invoked by uid 99); 11 Apr 2011 07:30:18 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Apr 2011 07:30:18 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [212.227.126.186] (HELO moutng.kundenserver.de) (212.227.126.186) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Apr 2011 07:30:10 +0000 Received: from [192.168.178.26] (port-92-200-124-232.dynamic.qsc.de [92.200.124.232]) by mrelayeu.kundenserver.de (node=mreu4) with ESMTP (Nemesis) id 0M5V8e-1Py7pm0lTM-00xc1l; Mon, 11 Apr 2011 09:29:50 +0200 Subject: Steps in execution time From: Christian Kumpe To: common-user@hadoop.apache.org Content-Type: text/plain; charset="UTF-8" Date: Mon, 11 Apr 2011 09:29:49 +0200 Message-ID: <1302506989.3434.28.camel@notebook> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:x57v/xKDY4R8LxW7qzXSSeYkkKZRcvvoP2L6cpUMiT5 357HVLxIHpWrUsni7jpjkAQxWZDn4u7IQitxk1/Htth4/7vuHc ZNjGK3UEQdzSzmbiMefUllEAdKEiOm51v5SI6JWmQCxsG7ECM3 0hXwtSNh7B8c+2YDPR65Fub9eIkln5KqoytbtC1ae0GJIvTWV9 iJK1fcVKj2gaOAijuolH4ya17hUQEmE5HqqVJEiixU= X-Virus-Checked: Checked by ClamAV on apache.org Hi, I'm doing some measurement on hadoop's execution time for my theses. I discovered some steps in the jobs execution time when raising the mappers' execution time continuously. Here is a plot of the execution times with 1, 30 and 60 parallel executing mappers: http://baumbart.drhuim.de/executiontime.gif The cluster consists of 10 nodes and an overall map task capacity of 60. I'm using hadoop 0.20.2. The many small steps about 1 second are probably caused by the polling interval of the JobClient in monitorAndPrintJob(..) which is about 1 second. But can anyone give me a hint, what's causing the bigger 3 second steps? I suppose it's a polling interval, too. But where? In the Jobtracker? In the Tasktrackers? Thanks for some help and comments, Christian