You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tajo.apache.org by "Hyunsik Choi (JIRA)" <ji...@apache.org> on 2014/02/04 08:08:10 UTC

[jira] [Commented] (TAJO-36) Improve ExternalSortExec with N-merge sort and final pass omission

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

Hyunsik Choi commented on TAJO-36:
----------------------------------

Created a review request against branch master in reviewboard 
https://reviews.apache.org/r/17693/


> Improve ExternalSortExec with N-merge sort and final pass omission
> ------------------------------------------------------------------
>
>                 Key: TAJO-36
>                 URL: https://issues.apache.org/jira/browse/TAJO-36
>             Project: Tajo
>          Issue Type: Improvement
>          Components: physical operator
>            Reporter: Hyunsik Choi
>            Assignee: Hyunsik Choi
>            Priority: Critical
>              Labels: gsoc, gsoc2013, mentor
>         Attachments: TAJO-36.patch
>
>
> Background:
> The current ExternalSortExec just uses the binary external merge sort algorithm (http://en.wikipedia.org/wiki/External_sorting#External_merge_sort). In other words, for each pass, ExternalSortExec just merges two files into one sorted file.
> Proposal:
> The goal of this proposal is to improve ExternalSortExec with the following improvements:
> * N-merge sort - we can merge N files though more memory at each pass. It will reduce the number of passes. Consequently, it will reduces considerable I/O overheads.
> * the final pass omission - a physical operator is pipelined by the parent operator. The final pass of the merge sort must also be invoked by the parent physical operator. So, we can omit the final pass of the merge sort.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)