Return-Path: Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: (qmail 24808 invoked from network); 3 Nov 2009 21:20:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 3 Nov 2009 21:20:17 -0000 Received: (qmail 55695 invoked by uid 500); 3 Nov 2009 21:20:16 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 55600 invoked by uid 500); 3 Nov 2009 21:20:16 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 55587 invoked by uid 99); 3 Nov 2009 21:20:16 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Nov 2009 21:20:16 +0000 X-ASF-Spam-Status: No, hits=-10.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI 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; Tue, 03 Nov 2009 21:19:54 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 23762234C4A8 for ; Tue, 3 Nov 2009 13:19:34 -0800 (PST) Message-ID: <1341824806.1257283174144.JavaMail.jira@brutus> Date: Tue, 3 Nov 2009 21:19:34 +0000 (UTC) From: "Todd Lipcon (JIRA)" To: common-issues@hadoop.apache.org Subject: [jira] Commented: (HADOOP-3205) FSInputChecker and FSOutputSummer should allow better access to user buffer MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12773199#action_12773199 ] Todd Lipcon commented on HADOOP-3205: ------------------------------------- Looking at the source of BufferedInputStream (at http://www.docjar.com/html/api/java/io/BufferedInputStream.java.html) it actually seems like BufferedInputStream is already handling pass-through to the underlying stream in the case that the read buffer is as large as its own buffer. That was the crucial bit I was missing that explains why performing the underlying reads in larger chunks would make a difference, even without removing the BIS. I'll give it a go and see if there is any discernible performance increase. bq. Plus, looking at how long this jira has been open, it is no blocker Of course :) > FSInputChecker and FSOutputSummer should allow better access to user buffer > --------------------------------------------------------------------------- > > Key: HADOOP-3205 > URL: https://issues.apache.org/jira/browse/HADOOP-3205 > Project: Hadoop Common > Issue Type: Bug > Components: fs > Reporter: Raghu Angadi > Assignee: Raghu Angadi > > Implementations of FSInputChecker and FSOutputSummer like DFS do not have access to full user buffer. At any time DFS can access only up to 512 bytes even though user usually reads with a much larger buffer (often controlled by io.file.buffer.size). This requires implementations to double buffer data if an implementation wants to read or write larger chunks of data from underlying storage. > We could separate changes for FSInputChecker and FSOutputSummer into two separate jiras. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.