Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 7DB3F200B29 for ; Wed, 15 Jun 2016 20:11:37 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 7C64A160A4D; Wed, 15 Jun 2016 18:11:37 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id CD1C0160A5D for ; Wed, 15 Jun 2016 20:11:36 +0200 (CEST) Received: (qmail 81555 invoked by uid 500); 15 Jun 2016 18:11:34 -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 74375 invoked by uid 99); 15 Jun 2016 18:11:14 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Jun 2016 18:11:14 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id B0E632C1F71 for ; Wed, 15 Jun 2016 18:11:09 +0000 (UTC) Date: Wed, 15 Jun 2016 18:11:09 +0000 (UTC) From: "Sean Busbey (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-15971) Regression: Random Read/WorkloadC slower in 1.x than 0.98 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 15 Jun 2016 18:11:37 -0000 [ https://issues.apache.org/jira/browse/HBASE-15971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15332230#comment-15332230 ] Sean Busbey commented on HBASE-15971: ------------------------------------- > How about we go with (1) and/or both RM's explicitly call this out in the next patch release announcement? Doing 1, adding a call out in the ref guide, and including a call out in future patch releases on the impacted lines works for me. > Regression: Random Read/WorkloadC slower in 1.x than 0.98 > --------------------------------------------------------- > > Key: HBASE-15971 > URL: https://issues.apache.org/jira/browse/HBASE-15971 > Project: HBase > Issue Type: Sub-task > Components: rpc > Affects Versions: 2.0.0, 1.3.0 > Reporter: stack > Assignee: stack > Priority: Critical > Fix For: 2.0.0, 1.3.0 > > Attachments: 098.hits.png, 098.png, HBASE-15971.branch-1.001.patch, HBASE-15971.branch-1.002.patch, Screen Shot 2016-06-10 at 5.08.24 PM.png, Screen Shot 2016-06-10 at 5.08.26 PM.png, branch-1.hits.png, branch-1.png, flight_recording_10172402220203_28.branch-1.jfr, flight_recording_10172402220203_29.09820.0.98.20.jfr, handlers.fp.png, hits.fp.png, hits.patched1.0.vs.unpatched1.0.vs.098.png, run_ycsb.sh > > > branch-1 is slower than 0.98 doing YCSB random read/workloadC. It seems to be doing about 1/2 the throughput of 0.98. > In branch-1, we have low handler occupancy compared to 0.98. Hacking in reader thread occupancy metric, is about the same in both. In parent issue, hacking out the scheduler, I am able to get branch-1 to go 3x faster so will dig in here. -- This message was sent by Atlassian JIRA (v6.3.4#6332)