hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ramkrishna.s.vasudevan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15452) Consider removing checkScanOrder from StoreScanner.next
Date Mon, 14 Mar 2016 04:34:33 GMT

    [ https://issues.apache.org/jira/browse/HBASE-15452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15192734#comment-15192734
] 

ramkrishna.s.vasudevan commented on HBASE-15452:
------------------------------------------------

[~lhofhansl]]
I think you forgot to attach the patch here. 

> Consider removing checkScanOrder from StoreScanner.next
> -------------------------------------------------------
>
>                 Key: HBASE-15452
>                 URL: https://issues.apache.org/jira/browse/HBASE-15452
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Lars Hofhansl
>
> In looking why we spent so much time in StoreScanner.next when doing a simple Phoenix
count\(*) query I came across checkScanOrder. Not only is this a function dispatch (that the
JIT would eventually inline), it also requires setting the prevKV member for every Cell encountered.
> Removing that logic a yields measurable end-to-end improvement of 5-20% (in 0.98).
> I will repeat this test on my work machine tomorrow.
> I think we're stable enough to remove that check anyway.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message