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 B58BD10BC2 for ; Wed, 4 Sep 2013 13:45:55 +0000 (UTC) Received: (qmail 57842 invoked by uid 500); 4 Sep 2013 13:45:53 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 57718 invoked by uid 500); 4 Sep 2013 13:45: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 57647 invoked by uid 99); 4 Sep 2013 13:45:52 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Sep 2013 13:45:52 +0000 Date: Wed, 4 Sep 2013 13:45:52 +0000 (UTC) From: "stack (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-9416) Use the disruptor library in the rcpServer 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-9416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13757767#comment-13757767 ] stack commented on HBASE-9416: ------------------------------ Thats coolio. So, instead of a set of handlers, we have the disruptor doing handoff? Was there an issue if the disruptor ring was not big enough and if we were not servicing it fast enough, it could overwrite outstanding events with new ones (maybe I imagined this)? Or does it block before it overruns the old entries? > Use the disruptor library in the rcpServer > ------------------------------------------ > > Key: HBASE-9416 > URL: https://issues.apache.org/jira/browse/HBASE-9416 > Project: HBase > Issue Type: Improvement > Components: regionserver > Affects Versions: 0.98.0 > Reporter: Nicolas Liochon > Assignee: Nicolas Liochon > Attachments: disrupt.patch > > > Nasty & hacky patch on top of the 0.96 to get some feedback on adding this third party. > I ran a test doing "gets" on an empty region. > With the current implementation, we're spending time in the LinkedBlockingQueue#put. I was able to do 150K operations per second. > Using the disruptor allowed me to go to 190 ops/s, i.e. a little be more than a 25% improvement. > Likely there are other improvements in this class as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira