Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EB130105FC for ; Sat, 12 Oct 2013 22:31:44 +0000 (UTC) Received: (qmail 94701 invoked by uid 500); 12 Oct 2013 22:31:43 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 94663 invoked by uid 500); 12 Oct 2013 22:31:43 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 94621 invoked by uid 99); 12 Oct 2013 22:31:43 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 12 Oct 2013 22:31:43 +0000 Date: Sat, 12 Oct 2013 22:31:43 +0000 (UTC) From: "Lars Hofhansl (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-9751) Excessive readpoints checks in StoreFileScanner MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-9751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-9751: --------------------------------- Fix Version/s: 0.96.1 0.94.13 0.98.0 > Excessive readpoints checks in StoreFileScanner > ------------------------------------------------ > > Key: HBASE-9751 > URL: https://issues.apache.org/jira/browse/HBASE-9751 > Project: HBase > Issue Type: Bug > Affects Versions: 0.98.0, 0.94.12, 0.96.0 > Reporter: Vladimir Rodionov > Assignee: Lars Hofhansl > Fix For: 0.98.0, 0.94.13, 0.96.1 > > Attachments: 9751-0.94.txt, 9751-trunk.txt > > > It seems that usage of skipKVsNewerThanReadpoint in StoreFileScanner can be greatly reduced or even eliminated all together (HFiles are immutable and no new KVs can be inserted after scanner instance is created). The same is true for MemStoreScanner which checks readpoint on every next() and seek(). Each readpoint check is ThreadLocal.get() and it is quite expensive. -- This message was sent by Atlassian JIRA (v6.1#6144)