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 1C17E199C3 for ; Fri, 1 Apr 2016 08:51:31 +0000 (UTC) Received: (qmail 10165 invoked by uid 500); 1 Apr 2016 08:51:25 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 10110 invoked by uid 500); 1 Apr 2016 08:51:25 -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 10096 invoked by uid 99); 1 Apr 2016 08:51:25 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Apr 2016 08:51:25 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 8AD4B2C1F5D for ; Fri, 1 Apr 2016 08:51:25 +0000 (UTC) Date: Fri, 1 Apr 2016 08:51:25 +0000 (UTC) From: "Duo Zhang (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (HBASE-15536) Make AsyncFSWAL as our default WAL 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-15536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15221395#comment-15221395 ] Duo Zhang edited comment on HBASE-15536 at 4/1/16 8:50 AM: ----------------------------------------------------------- So we are using more CPUs with asyncwal? But actually we spend less cycles with asyncwal(Yeah you said, less work)? What does the '2.597 GHz' mean? And for the IPC, I remember the time when I was a graduate student who was learning how to do 'software pipeline' and 'instruction scheduling' in a compiler... But usually these optimizations are only useful on loops and I can not find a heavy loop in {{AsyncFSWAL}} (maybe the append loop in consume method?)... And it is interesting that we have a less branch-miss rate but a less IPC... Maybe we need to find the hot spots in {{AsyncFSWAL}} first? Thanks. was (Author: apache9): So we are using more CPUs with asyncwal? But actually we spend less cycles with asyncwal(Yeah you said, less work)? What does the '2.597 GHz' mean? And for the IPC, I remember the time when I was a graduate student who was learning how to do 'software pipeline' and 'instruction scheduling' in a compiler... But usually these optimizations are only useful on loops and I can not find a heavy loop in {{AsyncFSWAL}}... And it is interesting that we have a less branch-miss rate but a less IPC... Maybe we need to find the hot spots in {{AsyncFSWAL}} first? Thanks. > Make AsyncFSWAL as our default WAL > ---------------------------------- > > Key: HBASE-15536 > URL: https://issues.apache.org/jira/browse/HBASE-15536 > Project: HBase > Issue Type: Sub-task > Reporter: Duo Zhang > > As it should be predicated on passing basic cluster ITBLL -- This message was sent by Atlassian JIRA (v6.3.4#6332)