Return-Path: X-Original-To: apmail-tajo-dev-archive@minotaur.apache.org Delivered-To: apmail-tajo-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 AADAB104EA for ; Wed, 2 Oct 2013 07:19:08 +0000 (UTC) Received: (qmail 61802 invoked by uid 500); 2 Oct 2013 07:19:07 -0000 Delivered-To: apmail-tajo-dev-archive@tajo.apache.org Received: (qmail 61770 invoked by uid 500); 2 Oct 2013 07:19:06 -0000 Mailing-List: contact dev-help@tajo.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@tajo.incubator.apache.org Delivered-To: mailing list dev@tajo.incubator.apache.org Received: (qmail 61760 invoked by uid 99); 2 Oct 2013 07:19:05 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Oct 2013 07:19:05 +0000 X-ASF-Spam-Status: No, hits=-2000.7 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.3] (HELO mail.apache.org) (140.211.11.3) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 02 Oct 2013 07:19:03 +0000 Received: (qmail 58082 invoked by uid 99); 2 Oct 2013 07:16:24 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Oct 2013 07:16:24 +0000 Date: Wed, 2 Oct 2013 07:16:23 +0000 (UTC) From: "Hyunsik Choi (JIRA)" To: dev@tajo.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (TAJO-223) Maximize disk read bandwidth utilization of StorageManagerV2 by moving Tuple creation role to next() MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/TAJO-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13783716#comment-13783716 ] Hyunsik Choi commented on TAJO-223: ----------------------------------- Hello Keuntae, Your proposal looks reasonable. If you want to take this issue, please feel free to ask me. > Maximize disk read bandwidth utilization of StorageManagerV2 by moving Tuple creation role to next() > ---------------------------------------------------------------------------------------------------- > > Key: TAJO-223 > URL: https://issues.apache.org/jira/browse/TAJO-223 > Project: Tajo > Issue Type: Improvement > Components: storage > Reporter: Keuntae Park > Labels: performance > > Currently, Tuple creation mechanism of StorageManagerV2 is as follows: > 1) At file scan, scheduled scanner reads data from disk, makes a Tuple, and insert it to the Tuple pool > 2) next() of the scanner just pulls an already created Tuple from the Tuple pool asynchronously > Because of Tuple creation time, scanner cannot fully use its time to read disk, which results in less disk read bandwidth utilization > So, if Tuple creation role is moved to next() and scanners spend their whole time to read file at file scan, > we can fully utilize disk read bandwidth -- This message was sent by Atlassian JIRA (v6.1#6144)