Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-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 2627D10766 for ; Fri, 9 Aug 2013 23:55:39 +0000 (UTC) Received: (qmail 19242 invoked by uid 500); 9 Aug 2013 23:55:36 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 19215 invoked by uid 500); 9 Aug 2013 23:55:36 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 19207 invoked by uid 99); 9 Aug 2013 23:55:36 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Aug 2013 23:55:36 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of rcoli@eventbrite.com designates 209.85.128.48 as permitted sender) Received: from [209.85.128.48] (HELO mail-qe0-f48.google.com) (209.85.128.48) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Aug 2013 23:55:31 +0000 Received: by mail-qe0-f48.google.com with SMTP id 9so2641254qea.7 for ; Fri, 09 Aug 2013 16:55:09 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=0UK8ogNbC9ERJ3ciFb6zeTnG+GHzkh/DSMo9dHEdoxE=; b=FVLHESxMUHk+Shj3PFzge9HxJnosEfgtcLyHpcT+ANe4x0zQZfXy6OdlKNQBxiRuG3 RXSq4kZebuY7uh/wQ5y/JgWaXnzOyQddVUYTnlQ85jJ/NQQnhXkcxEl86m17X2u53qti JpIDTQrGweCdwrWFIYrxYU/AfT8iqY7U8SOryzdkamtDnaGjrrll8pANBm01LJmeekdw ts8LD/xt5IdMp8At1cNRcTUAw5mINVFBCnAIk/E3h0r6utdAsX+D2uIHU68tatP0S2Hp qnqgEMXRkJztt+Txr9QLuAjhG5duUEvJds2v+ksZhEbKm1Z6BOIs20Wq/RxzdHvorLzi 7Opw== X-Gm-Message-State: ALoCoQnO8WqYfxkNhQe2024TlYKnIq7c7YkGmOFiVmaw0Np4d2EVqQPxbjYT4eCTQzkwd6UDdMrm MIME-Version: 1.0 X-Received: by 10.224.88.70 with SMTP id z6mr8820967qal.31.1376092509635; Fri, 09 Aug 2013 16:55:09 -0700 (PDT) Received: by 10.49.60.234 with HTTP; Fri, 9 Aug 2013 16:55:09 -0700 (PDT) In-Reply-To: References: Date: Fri, 9 Aug 2013 16:55:09 -0700 Message-ID: Subject: Re: Cassandra 1.2.5 which compressor is better? From: Robert Coli To: "user@cassandra.apache.org" Content-Type: multipart/alternative; boundary=001a11c3e84c371b6704e38c8164 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c3e84c371b6704e38c8164 Content-Type: text/plain; charset=ISO-8859-1 On Fri, Aug 9, 2013 at 4:43 PM, rash aroskar wrote: > I am setting up new cluster for cassandra 1.2.5, and first time using > cassandra compression. > I read about the compressors, and it gathered Snappy Compressor gives > better compression but is sslightly slower than LZ4 compressor. Just wanted > to know your experience and/or opinions as to *Snappy vs LZ4 , which > compressor is better in case of huge data, less writes but lots of reads.* > > https://issues.apache.org/jira/browse/CASSANDRA-5038 In general LZ4 is supposed to be better than Snappy, which is why it was added. The LZ4 site (iirc?) has some charts explaining its performance compared to Snappy in various cases. There's also the charts at https://github.com/ning/jvm-compressor-benchmark/wiki. =Rob --001a11c3e84c371b6704e38c8164 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Fri, Aug 9, 2013 at 4:43 PM, rash aroskar <rash= mi.aroskar@gmail.com> wrote:
I am setting up new cluster for cass= andra 1.2.5, and first time using cassandra compression.=A0
I read about the compressors, and it gathered Snappy Compressor gives = better compression but is sslightly slower than LZ4 compressor. Just wanted= to know your experience and/or opinions as to Snappy vs LZ4 , which com= pressor is better in case of huge data, less writes but lots of reads.= =A0

In general LZ4 is supposed to be better than Snappy, which is wh= y it was added. The LZ4 site (iirc?) has some charts explaining its perform= ance compared to Snappy in various cases. There's also the charts at=A0= https://g= ithub.com/ning/jvm-compressor-benchmark/wiki.

=3DRob=A0
--001a11c3e84c371b6704e38c8164--