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 D727217B8E for ; Wed, 1 Apr 2015 08:04:58 +0000 (UTC) Received: (qmail 56185 invoked by uid 500); 1 Apr 2015 08:04:53 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 56135 invoked by uid 500); 1 Apr 2015 08:04:53 -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 56123 invoked by uid 99); 1 Apr 2015 08:04:53 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Apr 2015 08:04:53 +0000 Date: Wed, 1 Apr 2015 08:04:53 +0000 (UTC) From: "Anoop Sam John (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-13291) Lift the scan ceiling 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-13291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14390189#comment-14390189 ] Anoop Sam John commented on HBASE-13291: ---------------------------------------- Yes as Ram said, at the StoreScanner level, cells come from diff StoreFiles. At StoreFileScanner level we can do this file context based decisions. > Lift the scan ceiling > --------------------- > > Key: HBASE-13291 > URL: https://issues.apache.org/jira/browse/HBASE-13291 > Project: HBase > Issue Type: Improvement > Components: Scanners > Affects Versions: 1.0.0 > Reporter: stack > Assignee: stack > Attachments: 13291.hacks.txt, 13291.inlining.txt, Screen Shot 2015-03-26 at 12.12.13 PM.png, Screen Shot 2015-03-26 at 3.39.33 PM.png, hack_to_bypass_bb.txt, nonBBposAndInineMvccVint.txt, q (1).png, traces.7.svg, traces.filterall.svg, traces.nofilter.svg, traces.small2.svg, traces.smaller.svg > > > Scanning medium sized rows with multiple concurrent scanners exhibits interesting 'ceiling' properties. A server runs at about 6.7k ops a second using 450% of possible 1600% of CPUs when 4 clients each with 10 threads doing scan 1000 rows. If I add '--filterAll' argument (do not return results), then we run at 1450% of possible 1600% possible but we do 8k ops a second. > Let me attach flame graphs for two cases. Unfortunately, there is some frustrating dark art going on. Let me try figure it... Filing issue in meantime to keep score in. -- This message was sent by Atlassian JIRA (v6.3.4#6332)