You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@asterixdb.apache.org by "Chen Luo (JIRA)" <ji...@apache.org> on 2017/10/17 23:06:00 UTC

[jira] [Created] (ASTERIXDB-2133) Unnecessary BinarySearch in GroupFrameAccessor

Chen Luo created ASTERIXDB-2133:
-----------------------------------

             Summary: Unnecessary BinarySearch in GroupFrameAccessor
                 Key: ASTERIXDB-2133
                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2133
             Project: Apache AsterixDB
          Issue Type: Bug
          Components: HYR - Hyracks
            Reporter: Chen Luo
            Assignee: Chen Luo


During the merge step of merge sort, if there is enough memory but only a few of runs to be merged, we would load multiple frames per run into the GroupFrameAccessor. Every time when we access a tuple, GroupFrameAccessor performs binary search over the inner frames to translate logical tuple index into the physical one (inner frame Id + index).

However, this is highly inefficiently. Since GroupFrameAccessor is only used by merge sort, it is expected that tuples are accessed sequentially, instead of randomly.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)