Return-Path: X-Original-To: apmail-hadoop-mapreduce-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-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 6B64A103F8 for ; Tue, 30 Apr 2013 18:46:36 +0000 (UTC) Received: (qmail 96771 invoked by uid 500); 30 Apr 2013 18:46:31 -0000 Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org Received: (qmail 96608 invoked by uid 500); 30 Apr 2013 18:46:31 -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 96600 invoked by uid 99); 30 Apr 2013 18:46:31 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Apr 2013 18:46:31 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jayunit100@gmail.com designates 209.85.215.44 as permitted sender) Received: from [209.85.215.44] (HELO mail-la0-f44.google.com) (209.85.215.44) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Apr 2013 18:46:25 +0000 Received: by mail-la0-f44.google.com with SMTP id ed20so732278lab.31 for ; Tue, 30 Apr 2013 11:46:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=BgHrCg1xWvm4Q9GJ8e9Mqxl153ekoyz3P9rPdS+h4pM=; b=hjXm2ad88Jvtm0NzuShaPLPjlApKQV+FZC9Lrr347u9sBNKWA7Ktrl0i2/UOwUuSgm sI77IRcVWUbO2+A9Ch3KltgHQQlDDWT5C/3fP55W+KQtMXeHoEIcJFh4vPFqa3Oe3rWk QlSQro6AabE+6S/Pps4lYuv2JQ4Mrp5hdq9wP0E9WL3JD1GaeIgoHa2K0L7q6OZK8Xo1 ZpI9guFJnMapfqFMBxS7yaFymcoqd+GRBc/89JoJ7w4KxCdZoGCKPI3pBX1KTM70kNNg FB6GSLxasmxDLJ5MRedqLTfvm16XbbdmbJZfd32j98pAfADXgx4vUg3BxlXgII6DDG9o icpA== MIME-Version: 1.0 X-Received: by 10.112.139.4 with SMTP id qu4mr85761lbb.37.1367347564728; Tue, 30 Apr 2013 11:46:04 -0700 (PDT) Received: by 10.112.173.194 with HTTP; Tue, 30 Apr 2013 11:46:04 -0700 (PDT) Date: Tue, 30 Apr 2013 14:46:04 -0400 Message-ID: Subject: partition as block? From: Jay Vyas To: "common-user@hadoop.apache.org" Content-Type: multipart/alternative; boundary=089e0112bf72e15a1004db9869eb X-Virus-Checked: Checked by ClamAV on apache.org --089e0112bf72e15a1004db9869eb Content-Type: text/plain; charset=ISO-8859-1 Hi guys: Im wondering - if I'm running mapreduce jobs on a cluster with large block sizes - can i increase performance with either: 1) A custom FileInputFormat 2) A custom partitioner 3) -DnumReducers Clearly, (3) will be an issue due to the fact that it might overload tasks and network traffic... but maybe (1) or (2) will be a precise way to "use" partitions as a "poor mans" block. Just a thought - not sure if anyone has tried (1) or (2) before in order to simulate blocks and increase locality by utilizing the partition API. -- Jay Vyas http://jayunit100.blogspot.com --089e0112bf72e15a1004db9869eb Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi guys:

Im wondering - if I'm r= unning mapreduce jobs on a cluster with large block sizes - can i increase = performance with either:

1) A custom FileInputFormat

2) A custom partitioner

3) -DnumReducers

Clearly, (3) will be an issue due to the fa= ct that it might overload tasks and network traffic... but maybe (1) or (2)= will be a precise way to "use" partitions as a "poor mans&q= uot; block.=A0

Just a thought - not sure if anyone has tried (1) or (2) bef= ore in order to simulate blocks and increase locality by utilizing the part= ition API.

--089e0112bf72e15a1004db9869eb--