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 C95B511FAD for ; Thu, 31 Jul 2014 22:00:53 +0000 (UTC) Received: (qmail 9557 invoked by uid 500); 31 Jul 2014 22:00:48 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 9421 invoked by uid 500); 31 Jul 2014 22:00:48 -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 9411 invoked by uid 99); 31 Jul 2014 22:00:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Jul 2014 22:00:47 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of harsh@cloudera.com designates 209.85.219.46 as permitted sender) Received: from [209.85.219.46] (HELO mail-oa0-f46.google.com) (209.85.219.46) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Jul 2014 22:00:45 +0000 Received: by mail-oa0-f46.google.com with SMTP id m1so2522155oag.5 for ; Thu, 31 Jul 2014 15:00:20 -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=MQWUimNNVp1/QbSw/DIR9K8geomK0zLr6ch+mLEfXt0=; b=G+Lk0I7UNr4ZH3nIM8XKzAnilEq22aYsBEJYzpD3b2gDo7+l7z5sDPqAvCZO2LkqQk l7L/7spdfHVZZ/bvPFPDGrgb3G0PulCY1IryEzgLKmDRrjFsNhpU+XASERxUo3qG8DKM 9+KdgqcWGb3RVJXBald5bJZSoKK9XOJy+YHuyq7DpyeQgNWls4zsjTCPlc86D0D83Drm S+N7uP+ftZKr8KaEKBk7ZRWMcllopCXS+8sIXiItajLM3pWI47TisJcgSCe/HvXAObAF TgCYrKpZb/LU/KLI01BkGymxH7hMHom7CuLVGF36GvB5BVeDKtMfbioU6IurUcxnpuVz jfVw== X-Gm-Message-State: ALoCoQl/BFeCmD3sVzIpIkz9IZJ0a1AKaWeR1jhEoxRfPfj4k23CAFeQdO61pRmX6GJtoAg2a81E X-Received: by 10.182.236.162 with SMTP id uv2mr1699247obc.12.1406844020328; Thu, 31 Jul 2014 15:00:20 -0700 (PDT) MIME-Version: 1.0 Received: by 10.60.45.1 with HTTP; Thu, 31 Jul 2014 15:00:00 -0700 (PDT) In-Reply-To: References: From: Harsh J Date: Fri, 1 Aug 2014 03:30:00 +0530 Message-ID: Subject: Re: Ideal number of mappers and reducers to increase performance To: "" Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org You can perhaps start with a generic 4+4 configuration (which matches your cores), and tune your way upwards or downwards from there based on your results. On Thu, Jul 31, 2014 at 8:35 PM, Sindhu Hosamane wrote: > Hello friends , > > If i am running my experiment on a server with 2 processors (4 cores each ) . > To say it has 2 processors and 8 cores . > What would be the ideal values for mapred.tasktracker.map.tasks.maximum and mapred.tasktracker.reduce.tasks.maximum to get maximum performance. > I am running cascalog queries on data of size 280 MB. > I have multiple datanodes running on same machine. > > Your help is very much appreciated. > > > Regards, > sindhu > -- Harsh J