[ https://issues.apache.org/jira/browse/TAJO-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13786041#comment-13786041
]
Hudson commented on TAJO-223:
-----------------------------
SUCCESS: Integrated in Tajo-trunk-postcommit #494 (See [https://builds.apache.org/job/Tajo-trunk-postcommit/494/])
TAJO-223: Maximize disk read bandwidth utilization of StorageManagerV2 by moving Tuple creation
role to next() (Keuntae Park via hyunsik) (hyunsik: https://git-wip-us.apache.org/repos/asf?p=incubator-tajo.git&a=commit&h=4449d9c48e9d0cdca7fa4a523fe4f9f389404f87)
* tajo-core/tajo-core-storage/src/test/java/org/apache/tajo/storage/v2/TestStorages.java
* tajo-core/tajo-core-storage/src/test/java/org/apache/tajo/storage/v2/TestCSVScanner.java
* tajo-core/tajo-core-storage/src/main/java/org/apache/tajo/storage/v2/FileScannerV2.java
* tajo-core/tajo-core-storage/src/main/java/org/apache/tajo/storage/v2/ScanScheduler.java
* tajo-core/tajo-core-storage/src/main/java/org/apache/tajo/storage/v2/RCFileScanner.java
* tajo-core/tajo-core-storage/src/main/java/org/apache/tajo/storage/v2/ScheduledInputStream.java
* tajo-core/tajo-core-backend/src/main/java/org/apache/tajo/client/TajoClient.java
* CHANGES.txt
* tajo-core/tajo-core-storage/src/main/java/org/apache/tajo/storage/v2/CSVFileScanner.java
* tajo-core/tajo-core-storage/src/test/java/org/apache/tajo/storage/index/TestBSTIndex.java
* tajo-core/tajo-core-storage/src/main/java/org/apache/tajo/storage/v2/RCFile.java
* tajo-core/tajo-core-storage/src/main/java/org/apache/tajo/storage/v2/StorageManagerV2.java
* tajo-core/tajo-core-storage/src/test/java/org/apache/tajo/storage/v2/TestCSVCompression.java
* tajo-core/tajo-core-storage/src/main/java/org/apache/tajo/storage/v2/DiskFileScanScheduler.java
> 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)
|