Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 36716 invoked from network); 7 Apr 2008 16:00:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 7 Apr 2008 16:00:10 -0000 Received: (qmail 79044 invoked by uid 500); 7 Apr 2008 16:00:09 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 79011 invoked by uid 500); 7 Apr 2008 16:00:08 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 79002 invoked by uid 99); 7 Apr 2008 16:00:08 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Apr 2008 09:00:08 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Apr 2008 15:59:25 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 1AF57234C0C1 for ; Mon, 7 Apr 2008 08:57:25 -0700 (PDT) Message-ID: <1306142167.1207583845109.JavaMail.jira@brutus> Date: Mon, 7 Apr 2008 08:57:25 -0700 (PDT) From: "Raghu Angadi (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Commented: (HADOOP-1702) Reduce buffer copies when data is written to DFS MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12586439#action_12586439 ] Raghu Angadi commented on HADOOP-1702: -------------------------------------- Whats wrong with a internal variable with default of 64k? How do we know 64k is the best for all platforms, though its a pretty good value? > Reduce buffer copies when data is written to DFS > ------------------------------------------------ > > Key: HADOOP-1702 > URL: https://issues.apache.org/jira/browse/HADOOP-1702 > Project: Hadoop Core > Issue Type: Bug > Components: dfs > Affects Versions: 0.14.0 > Reporter: Raghu Angadi > Assignee: Raghu Angadi > Attachments: HADOOP-1702.patch > > > HADOOP-1649 adds extra buffering to improve write performance. The following diagram shows buffers as pointed by (numbers). Each eatra buffer adds an extra copy since most of our read()/write()s match the io.bytes.per.checksum, which is much smaller than buffer size. > {noformat} > (1) (2) (3) (5) > +---||----[ CLIENT ]---||----<>-----||---[ DATANODE ]---||--<>-> to Mirror > | (buffer) (socket) | (4) > | +--||--+ > ===== | > ===== ===== > (disk) ===== > {noformat} > Currently loops that read and write block data, handle one checksum chunk at a time. By reading multiple chunks at a time, we can remove buffers (1), (2), (3), and (5). > Similarly some copies can be reduced when clients read data from the DFS. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.