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 E114517EAB for ; Fri, 20 Mar 2015 20:39:41 +0000 (UTC) Received: (qmail 93545 invoked by uid 500); 20 Mar 2015 20:39:38 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 93498 invoked by uid 500); 20 Mar 2015 20:39:38 -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 93486 invoked by uid 99); 20 Mar 2015 20:39:38 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Mar 2015 20:39:38 +0000 Date: Fri, 20 Mar 2015 20:39:38 +0000 (UTC) From: "stack (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=14372055#comment-14372055 ] stack commented on HBASE-13291: ------------------------------- [~ram_krish] Thanks for keeping an eye on me. Will try your suggestion in a while. Meantime, am able to get ScannerV2.next and all below inlined (see attached flame graph and patch breaking stuff into smaller methods) but the improvement is small. Could spend more time going down this path but payback is not of the proportions that I'm after... so passing on this for time being. Will put up graph of benefit in a while. > 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: traces.filterall.svg, traces.nofilter.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)