[
https://issues.apache.org/jira/browse/IMPALA-14386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18039529#comment-18039529
]
ASF subversion and git services commented on IMPALA-14386:
----------------------------------------------------------
Commit c4c9adf5922743b81c791c99e97b44df32ee8126 in impala's branch
refs/heads/master from Gabriella Gyorgyevics
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=c4c9adf59 ]
IMPALA-14386: Add benchmarks for Byte Stream Split encoding
This patch adds benchmarks to the Byte Stream Split encoding. It
compares different ways to use the decoder.
I added benchmarks for the following comparisons:
* Compile VS Runtime initialized decoder
* Float VS Int VS Double VS Long VS 6 and 11 byte size types
* Repeating VS Sequential VS Random ordered data
* Decoding one by one VS in batch VS with stride (!= byte_size)
* Small VS Medium (10x small) VS Large (100x small) stride
Conclusions:
* Passing the byte size as a template parameter is almost 5 times
as fast as passing it in the constructor.
* The size of the type heavily influences the speed
* The data variation doesn't influence the speed at all
* Reading values in batch is much faster than one-by-one
* The stride sizes have a small influence on the speed
For more details and graphs, go to
https://docs.google.com/spreadsheets/d/129LwvR6gpZInlRhlVWktn6Haugwo_fnloAAYfI0Qp2s
Change-Id: I708af625348b0643aa3f37525b8a6e74f0c47057
Reviewed-on: http://gerrit.cloudera.org:8080/23401
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Add benchmarks for Byte Stream Split encoding
> ---------------------------------------------
>
> Key: IMPALA-14386
> URL: https://issues.apache.org/jira/browse/IMPALA-14386
> Project: IMPALA
> Issue Type: Sub-task
> Reporter: Gyorgyevics Gabriella
> Assignee: Gyorgyevics Gabriella
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
