Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 17 Nov 2015 11:59:10 +0000 (UTC)
From: "ramkrishna.s.vasudevan (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12913672.1447760210000.92152.1447761550941@Atlassian.JIRA>
In-Reply-To: <JIRA.12913672.1447760210000@Atlassian.JIRA>
References: <JIRA.12913672.1447760210000@Atlassian.JIRA>
 <JIRA.12913672.1447760210834@arcas>
Subject: [jira] [Updated] (HBASE-14826) Small improvement in KVHeap seek()
 API
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-14826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ramkrishna.s.vasudevan updated HBASE-14826:
-------------------------------------------
    Assignee: ramkrishna.s.vasudevan
      Status: Patch Available  (was: Open)

> Small improvement in KVHeap seek() API
> --------------------------------------
>
>                 Key: HBASE-14826
>                 URL: https://issues.apache.org/jira/browse/HBASE-14826
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: ramkrishna.s.vasudevan
>            Priority: Minor
>         Attachments: HBASE-14826.patch
>
>
> Currently in seek/reseek() APIs we tend to do lot of priorityqueue related operations. We initially add the current scanner to the heap, then poll and again add the scanner back if the seekKey is greater than the topkey in that scanner. Since the KVs are always going to be in increasing order and in ideal scan flow every seek/reseek is followed by a next() call it should be ok if we start with checking the current scanner and then do a poll to get the next scanner. Just avoid the initial PQ.add(current) call. This could save some comparisons. 


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