[
https://issues.apache.org/jira/browse/HBASE-14628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14965745#comment-14965745
]
Lars Hofhansl commented on HBASE-14628:
---------------------------------------
And agreed on removing getValueShallowCopy. Return a ByteBuffer from any method
leaks internal implementation that we should avoid (even in in internal
interface).
> [0.98] Save object creation for scanning with block encodings
> -------------------------------------------------------------
>
> Key: HBASE-14628
> URL: https://issues.apache.org/jira/browse/HBASE-14628
> Project: HBase
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Fix For: 0.98.16
>
> Attachments: 14628-0.98-v2.txt, 14628-0.98.txt
>
>
> I noticed that (at least in 0.98 - master is entirely different) we create
> ByteBuffer just to create a byte[], which is then used to create a KeyValue.
> We can save the creation of the ByteBuffer and hence save allocating an extra
> object for each KV we find by creating the byte[] directly.
> In a Phoenix count\(*) query that saved from 10% of runtime.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
