Return-Path: X-Original-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 07B64E426 for ; Tue, 4 Dec 2012 17:40:00 +0000 (UTC) Received: (qmail 615 invoked by uid 500); 4 Dec 2012 17:40:00 -0000 Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org Received: (qmail 99686 invoked by uid 500); 4 Dec 2012 17:40:00 -0000 Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-dev@hadoop.apache.org Delivered-To: mailing list hdfs-dev@hadoop.apache.org Received: (qmail 99673 invoked by uid 99); 4 Dec 2012 17:39:59 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Dec 2012 17:39:59 +0000 X-ASF-Spam-Status: No, hits=0.0 required=5.0 tests= X-Spam-Check-By: apache.org Received-SPF: unknown -allip4:64.6.108.239 (athena.apache.org: encountered unrecognized mechanism during SPF processing of domain of hsn@filez.com) Received: from [64.6.108.239] (HELO ponto.amerinoc.com) (64.6.108.239) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Dec 2012 17:39:51 +0000 Received: from fbsd9.localdomain (205.83.broadband7.iol.cz [88.102.83.205]) (authenticated bits=128) by ponto.amerinoc.com (8.14.5/8.14.5) with ESMTP id qB4HdR0s004780 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 4 Dec 2012 18:39:30 +0100 (CET) (envelope-from hsn@filez.com) Received: from [127.0.0.1] ([10.0.0.1]) by fbsd9.localdomain (8.14.5/8.14.5) with ESMTP id qB4HdMOl002029 for ; Tue, 4 Dec 2012 18:39:22 +0100 (CET) (envelope-from hsn@filez.com) Message-ID: <50BE3546.7000200@filez.com> Date: Tue, 04 Dec 2012 18:39:18 +0100 From: Radim Kolar User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: hdfs-dev@hadoop.apache.org Subject: Re: profiling hdfs write path References: <50B2908A.4070507@filez.com> <50B77C9D.6080502@filez.com> <50BE2DB5.2030704@filez.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 121204-0, 04.12.2012), Outbound message X-Antivirus-Status: Clean X-Virus-Checked: Checked by ClamAV on apache.org > If you're just going to insult us, please stay away. We don't need > your help unless you're going to be constructive. Good units tests will catch code modifications like: from: long getLastByteOffsetBlock() { return lastByteOffsetInBlock; } to from: long getLastByteOffsetBlock() { return lastByteOffsetInBlock-1; } I did 10 of such changes and about 60% were undetected.