You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tajo.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/03/17 06:03:39 UTC
[jira] [Commented] (TAJO-1407) Minor performance improvement of
MemSortExec
[ https://issues.apache.org/jira/browse/TAJO-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14364571#comment-14364571 ]
ASF GitHub Bot commented on TAJO-1407:
--------------------------------------
GitHub user navis opened a pull request:
https://github.com/apache/tajo/pull/426
TAJO-1407 Minor performance improvement of MemSortExec
Simple micro benchmark shows 15~30% performance improvement, but this uses more memory. (Also can make little difference on appearance order of non-key values, caused by different sort implementation)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/navis/tajo TAJO-1407
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tajo/pull/426.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #426
----
commit 219ff84a6992b2ff44550bbc98e60b006f699863
Author: navis.ryu <na...@apache.org>
Date: 2015-03-17T04:59:38Z
TAJO-1407 Minor performance improvement of MemSortExec
----
> Minor performance improvement of MemSortExec
> --------------------------------------------
>
> Key: TAJO-1407
> URL: https://issues.apache.org/jira/browse/TAJO-1407
> Project: Tajo
> Issue Type: Improvement
> Components: physical operator
> Reporter: Navis
> Assignee: Navis
> Priority: Minor
>
> Currently, tajo uses Collections.sort() with TupleCompartor, which can incur some overheads on comparing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)