Return-Path: Delivered-To: apmail-hadoop-core-user-archive@www.apache.org Received: (qmail 68511 invoked from network); 15 Jul 2008 01:44:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 15 Jul 2008 01:44:08 -0000 Received: (qmail 9542 invoked by uid 500); 15 Jul 2008 01:44:04 -0000 Delivered-To: apmail-hadoop-core-user-archive@hadoop.apache.org Received: (qmail 9503 invoked by uid 500); 15 Jul 2008 01:44:04 -0000 Mailing-List: contact core-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-user@hadoop.apache.org Delivered-To: mailing list core-user@hadoop.apache.org Received: (qmail 9492 invoked by uid 99); 15 Jul 2008 01:44:04 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Jul 2008 18:44:04 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of grafan@gmail.com designates 74.125.46.28 as permitted sender) Received: from [74.125.46.28] (HELO yw-out-2324.google.com) (74.125.46.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Jul 2008 01:43:11 +0000 Received: by yw-out-2324.google.com with SMTP id 9so2949522ywe.29 for ; Mon, 14 Jul 2008 18:43:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=OFm45hRISOU1OIDKrI54VPC6mmjPF49kxIGCVvTGHF4=; b=fri68BBi6SlLrm11Yp0/6jzNqa8HBuJIiwh5WGXlA1V7HiLa4Qi3yyyYZwqZQ0EDBO ZYj/JWfjfO8+tXCT3LwFKUaau1knFeDdmeWd80IFJoXvXPO1end5fk8HaFRHBNGHhNcL 1tB/lJDr8SYDX8JEu033M/O56dTodcYpq4q5U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=CFpkIn9fWcWmaRGQVWUQ/3I1fsroAT1hIlvd5wOfmdjHI9MXEjOgWpvk0Ek/TFsS5Q IBjfhJpJc/0DDNNE3XY4VvMmaAts2wcYlgSHK0RGoH9jxQCO5lz3LimHYtfI3nS8mat3 Vu2x1cWA6h51axFxVCjOuon72/CfL7NlhtNEk= Received: by 10.151.142.2 with SMTP id u2mr6791230ybn.207.1216086214671; Mon, 14 Jul 2008 18:43:34 -0700 (PDT) Received: by 10.150.181.9 with HTTP; Mon, 14 Jul 2008 18:43:34 -0700 (PDT) Message-ID: <6eb82e0807141843p4066990cna04d1d61f7810acb@mail.gmail.com> Date: Tue, 15 Jul 2008 09:43:34 +0800 From: "Rong-en Fan" To: core-user@hadoop.apache.org Subject: different dfs block size MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Checked: Checked by ClamAV on apache.org Hi, I'm wondering what would be the memory consumption of dfs.block.size for a fixed set of data in NameNode? I know it is determined by # of blocks and # of replications, but how many memory does one block will use in NameNode? In addition, what would be the pros/cons of bigger/smaller block size? Thanks, Rong-En Fan