You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2015/08/26 08:51:46 UTC
[jira] [Updated] (HBASE-14315) Save one call to KeyValueHeap.peek
per row
[ https://issues.apache.org/jira/browse/HBASE-14315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Hofhansl updated HBASE-14315:
----------------------------------
Description:
Another one of my micro optimizations.
In StoreScanner.next(...) we can actually save a call to KeyValueHeap.peek, which in my runs of scan heavy loads shows up at top.
Based on the run and data this can safe between 3 and 10% of runtime.
was:
Another one of my micro optimizations.
In StoreScanner.next(...) we can actually safe a call to KeyValueHeap.peek, which in my runs of scan heavy loads shows up at top.
Based on the run and data this can safe between 3 and 10% of runtime.
> Save one call to KeyValueHeap.peek per row
> ------------------------------------------
>
> Key: HBASE-14315
> URL: https://issues.apache.org/jira/browse/HBASE-14315
> Project: HBase
> Issue Type: Bug
> Reporter: Lars Hofhansl
>
> Another one of my micro optimizations.
> In StoreScanner.next(...) we can actually save a call to KeyValueHeap.peek, which in my runs of scan heavy loads shows up at top.
> Based on the run and data this can safe between 3 and 10% of runtime.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)