[ https://issues.apache.org/jira/browse/TAJO-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hyunsik Choi updated TAJO-223: ------------------------------ Resolution: Fixed Status: Resolved (was: Patch Available) committed. Thank you for your contribution. > 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 > Fix For: 0.2-incubating > > Attachments: TAJO-223_2.patch, 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)