Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Sun, 13 Mar 2016 17:40:33 +0000 (UTC)
From: "Lars Hofhansl (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12949716.1457890816000.2741.1457890833855@Atlassian.JIRA>
In-Reply-To: <JIRA.12949716.1457890816000@Atlassian.JIRA>
References: <JIRA.12949716.1457890816000@Atlassian.JIRA>
 <JIRA.12949716.1457890816033@arcas>
Subject: [jira] [Created] (HBASE-15452) Consider removing checkScanOrder
 from StoreScanner.next
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Lars Hofhansl created HBASE-15452:
-------------------------------------

             Summary: 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)