Return-Path: X-Original-To: apmail-hbase-commits-archive@www.apache.org Delivered-To: apmail-hbase-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1FAAA18E12 for ; Sat, 13 Feb 2016 20:10:15 +0000 (UTC) Received: (qmail 85123 invoked by uid 500); 13 Feb 2016 20:10:12 -0000 Delivered-To: apmail-hbase-commits-archive@hbase.apache.org Received: (qmail 85054 invoked by uid 500); 13 Feb 2016 20:10:12 -0000 Mailing-List: contact commits-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 commits@hbase.apache.org Received: (qmail 84508 invoked by uid 99); 13 Feb 2016 20:10:12 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 13 Feb 2016 20:10:12 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 3C505E0BB2; Sat, 13 Feb 2016 20:10:12 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: syuanjiang@apache.org To: commits@hbase.apache.org Date: Sat, 13 Feb 2016 20:10:27 -0000 Message-Id: <4a61ddedb10b4c819fd6f82fee3f7311@git.apache.org> In-Reply-To: <557e28142c9d48949e826ddfaa38a52a@git.apache.org> References: <557e28142c9d48949e826ddfaa38a52a@git.apache.org> X-Mailer: ASF-Git Admin Mailer Subject: [16/22] hbase git commit: HBASE-15255 Add pointer to linkedin blog on putting jvm logs on fast disk HBASE-15255 Add pointer to linkedin blog on putting jvm logs on fast disk Project: http://git-wip-us.apache.org/repos/asf/hbase/repo Commit: http://git-wip-us.apache.org/repos/asf/hbase/commit/ab50c7c8 Tree: http://git-wip-us.apache.org/repos/asf/hbase/tree/ab50c7c8 Diff: http://git-wip-us.apache.org/repos/asf/hbase/diff/ab50c7c8 Branch: refs/heads/hbase-12439 Commit: ab50c7c8c64aa00da14167b01a9e599098afe4bc Parents: 25dfc11 Author: stack Authored: Thu Feb 11 13:18:28 2016 -0800 Committer: stack Committed: Thu Feb 11 13:18:28 2016 -0800 ---------------------------------------------------------------------- src/main/asciidoc/_chapters/performance.adoc | 8 ++++++++ 1 file changed, 8 insertions(+) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/hbase/blob/ab50c7c8/src/main/asciidoc/_chapters/performance.adoc ---------------------------------------------------------------------- diff --git a/src/main/asciidoc/_chapters/performance.adoc b/src/main/asciidoc/_chapters/performance.adoc index 5155f0a..ee7933c 100644 --- a/src/main/asciidoc/_chapters/performance.adoc +++ b/src/main/asciidoc/_chapters/performance.adoc @@ -48,6 +48,11 @@ Use a 64-bit platform (and 64-bit JVM). Watch out for swapping. Set `swappiness` to 0. +[[perf.os.cpu]] +=== CPU +Make sure you have set up your Hadoop to use native, hardware checksumming. +See link:[hadoop.native.lib]. + [[perf.network]] == Network @@ -137,6 +142,9 @@ It describes configurations to lower the amount of young GC during write-heavy l If you do not have HBASE-8163 installed, and you are trying to improve your young GC times, one trick to consider -- courtesy of our Liang Xie -- is to set the GC config `-XX:PretenureSizeThreshold` in _hbase-env.sh_ to be just smaller than the size of `hbase.hregion.memstore.mslab.chunksize` so MSLAB allocations happen in the tenured space directly rather than first in the young gen. You'd do this because these MSLAB allocations are going to likely make it to the old gen anyways and rather than pay the price of a copies between s0 and s1 in eden space followed by the copy up from young to old gen after the MSLABs have achieved sufficient tenure, save a bit of YGC churn and allocate in the old gen directly. +Other sources of long GCs can be the JVM itself logging. +See link:https://engineering.linkedin.com/blog/2016/02/eliminating-large-jvm-gc-pauses-caused-by-background-io-traffic[Eliminating Large JVM GC Pauses Caused by Background IO Traffic] + For more information about GC logs, see <>. Consider also enabling the off-heap Block Cache.