[jira] [Comment Edited] (TAJO-223) Maximize disk read bandwidth utilization of StorageManagerV2 by moving Tuple creation role to next()

["Keuntae Park (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TAJO-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13785868#comment-13785868 ] 

Keuntae Park edited comment on TAJO-223 at 10/4/13 3:36 AM:
------------------------------------------------------------

Thanks Hyunsik,
I just add a patch for the issue


was (Author: sirpkt):
This is the patch for the issue

> 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
>            Assignee: Keuntae Park
>              Labels: performance
>         Attachments: TAJO-223.patch
>
>
> 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)