Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 018A911E06 for ; Sat, 14 Jun 2014 19:52:26 +0000 (UTC) Received: (qmail 26238 invoked by uid 500); 14 Jun 2014 19:52:24 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 26173 invoked by uid 500); 14 Jun 2014 19:52:24 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 26161 invoked by uid 99); 14 Jun 2014 19:52:24 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 14 Jun 2014 19:52:24 +0000 X-ASF-Spam-Status: No, hits=2.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_REPLY,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of konstt2000@gmail.com designates 74.125.82.41 as permitted sender) Received: from [74.125.82.41] (HELO mail-wg0-f41.google.com) (74.125.82.41) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 14 Jun 2014 19:52:21 +0000 Received: by mail-wg0-f41.google.com with SMTP id a1so4077214wgh.12 for ; Sat, 14 Jun 2014 12:51:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=1Zjif/OpXH4S+WmcJPMBXHMhLw6TgsOgxXs+bKRAU9w=; b=ylhNwdjrzsUAl6vN/a/gDcm8K6+s/a37dRdPu51TyFA1nDjAyKsDRnbIpKhWPUX911 /Jus6iFP0emVmTxp9ZqyJiYouMojgOn43X68qRWkU4E4/ttnkBGIgy5z9gDnDE50wvk8 T6WkaA8IAKH5dm7CtWYligY8F3kzc/sRjPmOZYk/72Qa5FKy67d4DqBHhKnbQ/v0IQSw i5X7TQ5x1COscyaT0D32rIY+9X14ZEhqusJPA+3iH+RoPHjHXcrvlKxx3VrlljVaIBGj pC19BRW5RYrj/fuJy6K4LVVClbMD50SaAmpWRWLwCYfcRBVVrcWrOV0H1dPaw9aMUvip nLHA== MIME-Version: 1.0 X-Received: by 10.180.73.66 with SMTP id j2mr14559456wiv.36.1402775517872; Sat, 14 Jun 2014 12:51:57 -0700 (PDT) Received: by 10.217.54.130 with HTTP; Sat, 14 Jun 2014 12:51:57 -0700 (PDT) In-Reply-To: References: Date: Sat, 14 Jun 2014 21:51:57 +0200 Message-ID: Subject: Re: Does compression ever improve performance? From: Guillermo Ortiz To: "user@hbase.apache.org" Content-Type: multipart/alternative; boundary=f46d0438921b714c1304fbd120ae X-Virus-Checked: Checked by ClamAV on apache.org --f46d0438921b714c1304fbd120ae Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I would like to see the times they got doing some scans or get with the benchmark about compression and block code to figure out how much time to save if your data are smaller but you have to decompress them. El s=C3=A1bado, 14 de junio de 2014, Kevin O'dell escribi=C3=B3: > Hi Jeremy, > > I always recommend turning on snappy compression, I have ~20% > performance increases. > On Jun 14, 2014 10:25 AM, "Ted Yu" > > wrote: > > > You may have read Doug Meil's writeup where he tried out different > > ColumnFamily > > compressions : > > > > https://blogs.apache.org/hbase/ > > > > Cheers > > > > > > On Fri, Jun 13, 2014 at 11:33 AM, jeremy p < > athomewithagroovebox@gmail.com > > > > > wrote: > > > > > Thank you -- I'll go ahead and try compression. > > > > > > --Jeremy > > > > > > > > > On Fri, Jun 13, 2014 at 10:59 AM, Dima Spivak > > > > wrote: > > > > > > > I'd highly recommend it. In general, compressing your column famili= es > > > will > > > > improve performance by reducing the resources required to get data > from > > > > disk (even when taking into account the CPU overhead of compressing > and > > > > decompressing). > > > > > > > > -Dima > > > > > > > > > > > > On Fri, Jun 13, 2014 at 10:35 AM, jeremy p < > > > athomewithagroovebox@gmail.com > > > > > > > > > wrote: > > > > > > > > > Hey all, > > > > > > > > > > Right now, I'm not using compression on any of my tables, because > our > > > > data > > > > > doesn't take up a huge amount of space. However, I would turn on > > > > > compression if there was a chance it would improve HBase's > > performance. > > > > By > > > > > performance, I'm talking about the speed with which HBase respond= s > to > > > > > requests and retrieves data. > > > > > > > > > > Should I turn compression on? > > > > > > > > > > --Jeremy > > > > > > > > > > > > > > > --f46d0438921b714c1304fbd120ae--