[jira] [Commented] (ASTERIXDB-2149) Improve NormalizedKey on Sorting

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/ASTERIXDB-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316607#comment-16316607
 ] 

ASF subversion and git services commented on ASTERIXDB-2149:


Commit 90af4b24f8b6a9259bfc307ea76bcc0f7b3e2806 in asterixdb's branch 
refs/heads/master from [~luochen01]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=90af4b2 ]

[ASTERIXDB-2149] Refactor key normalizer with longer keys

- user model changes: no
- storage format changes: no
- interface changes: yes. The interface of key normalized is changed.

Details:
- Refactored key normalizer to work with longer normalized keys composed
of multiple integers.
- Add tests for key normalizers
- Add key normalizer for UUID type to improve sort performance.

Change-Id: Idba747285af74195ef9953ed9bf5f6f217511380
Reviewed-on: https://asterix-gerrit.ics.uci.edu/2225
Sonar-Qube: Jenkins 
Tested-by: Jenkins 
Contrib: Jenkins 
Integration-Tests: Jenkins 
Reviewed-by: abdullah alamoudi 


> Improve NormalizedKey on Sorting
> 
>
> Key: ASTERIXDB-2149
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2149
> Project: Apache AsterixDB
>  Issue Type: Improvement
>Reporter: Chen Luo
>Assignee: Chen Luo
>
> Normalized keys are used to improve sorting performance by avoiding random 
> memory accesses. However, currently it has several limitations:
> # Normalized key computer is missing for some types, e.g., UUID
> # It only helps with unequal keys. When two keys are equal, it still requires 
> random accesses to do comparison.



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

[jira] [Commented] (ASTERIXDB-2149) Improve NormalizedKey on Sorting

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/ASTERIXDB-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267578#comment-16267578
 ] 

ASF subversion and git services commented on ASTERIXDB-2149:


Commit ed469381235990ce5ecd2f242b679190ef2ca263 in asterixdb's branch 
refs/heads/master from [~luochen01]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=ed46938 ]

[ASTERIXDB-2149] Enable multiple normalized keys in sort

- user model changes: no
- storage format changes: no
- interface changes: yes. The interface of sort is changed.

Currently, during the (in-memory) sort, we use an int normalized keys to
speed up comparisions by avoiding random memory accesses. However, this
technique is inefficient if the first 4 bytes of the sorting keys are
not distinctive. From performance point of view, it's better to use
longer normalized keys when it's possible (2-3x improvements).

This is enabled by this patch by:
- Allowing multiple normalized keys during sort, and the length of each
normalized key can be longer (multiple integers).
- Enable memory budgeting of pointer directories as well during sort
(but for performance, we still use int[], instead of byte[] from frame).

The next patch will enable the AsterixDB layer to use this feature to
speed up sort performance.

Change-Id: I4354242ff731b4b006b8446b58f65873047dde78
Reviewed-on: https://asterix-gerrit.ics.uci.edu/2127
Sonar-Qube: Jenkins 
Tested-by: Jenkins 
Contrib: Jenkins 
Integration-Tests: Jenkins 
Reviewed-by: abdullah alamoudi 


> Improve NormalizedKey on Sorting
> 
>
> Key: ASTERIXDB-2149
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2149
> Project: Apache AsterixDB
>  Issue Type: Improvement
>Reporter: Chen Luo
>Assignee: Chen Luo
>
> Normalized keys are used to improve sorting performance by avoiding random 
> memory accesses. However, currently it has several limitations:
> # Normalized key computer is missing for some types, e.g., UUID
> # It only helps with unequal keys. When two keys are equal, it still requires 
> random accesses to do comparison.



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