[
https://issues.apache.org/jira/browse/HBASE-8694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13724843#comment-13724843
]
Nick Dimiduk commented on HBASE-8694:
-------------------------------------
Here's the output of an initial benchmark suite over
[Long|https://microbenchmarks.appspot.com/runs/57d5dc89-d731-4069-8253-907568de0108]
and
[Double|https://microbenchmarks.appspot.com/runs/829251d9-c633-4289-b731-f041ae1d69fe]
encodings. This is vs. code from yesterday; it does not include today's
refactor to ByteRange or the introduction of Guava Precondition checking.
Benchmark code is in a [repository on
github|https://github.com/ndimiduk/encoding-microbench] and include basic
instructions for reproduction.
Preliminary results indicate Phoenix's DECIMAL is ~2x faster and uses ~3x fewer
heap objects than my Numeric implementation. Nice job [~giacomotaylor]! I'll
look into cribbing off of your implementation tomorrow ;) In the mean time,
have a look at the implementations and make sure I'm doing the other encoding
libraries justice.
> Performance evaluation of encoding implementations
> --------------------------------------------------
>
> Key: HBASE-8694
> URL: https://issues.apache.org/jira/browse/HBASE-8694
> Project: HBase
> Issue Type: Sub-task
> Components: Client
> Reporter: Nick Dimiduk
> Assignee: Nick Dimiduk
> Fix For: 0.95.2
>
>
> This ticket encapsulates a micro-benchmark of serialization implementation
> and any performance enhancements that fall out. Specifically, the
> implementation posted in HBASE-8201 should be compared to the performance of
> Phoenix's
> [PDataType|https://github.com/forcedotcom/phoenix/blob/master/src/main/java/com/salesforce/phoenix/schema/PDataType.java]
> implementations.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
