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 DA0FA200B50 for ; Fri, 29 Jul 2016 19:17:22 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id D896D160AA7; Fri, 29 Jul 2016 17:17:22 +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 21259160AA6 for ; Fri, 29 Jul 2016 19:17:21 +0200 (CEST) Received: (qmail 13316 invoked by uid 500); 29 Jul 2016 17:17:20 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 13282 invoked by uid 99); 29 Jul 2016 17:17:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Jul 2016 17:17:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 7E6222C0D5D for ; Fri, 29 Jul 2016 17:17:20 +0000 (UTC) Date: Fri, 29 Jul 2016 17:17:20 +0000 (UTC) From: "Elliott Clark (JIRA)" To: dev@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HBASE-16305) Multi threaded scan performance bottlenecked on Connection MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 29 Jul 2016 17:17:23 -0000 Elliott Clark created HBASE-16305: ------------------------------------- Summary: Multi threaded scan performance bottlenecked on Connection Key: HBASE-16305 URL: https://issues.apache.org/jira/browse/HBASE-16305 Project: HBase Issue Type: Bug Reporter: Elliott Clark Pretty simple repro. On a single region server host ~10 or more regions. Then for each region spawn a thread that starts a scan. Try an pull the scan as fast as possible. If all the scans are created through the same connection then it's slow. If all the scans are created through different connections then the scan speed is doubled. Since we recommend a single connection per application this is pretty surprising behavior. -- This message was sent by Atlassian JIRA (v6.3.4#6332)