linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Purdie <richard@openedhand.com>
To: "Bill Rugolsky Jr." <brugolsky@telemetry-investments.com>
Cc: Krzysztof Halasa <khc@pm.waw.pl>,
	Nitin Gupta <nitingupta910@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC] LZO1X de/compression support
Date: Sat, 19 May 2007 22:52:12 +0100	[thread overview]
Message-ID: <1179611532.5852.25.camel@localhost.localdomain> (raw)
In-Reply-To: <20070519185514.GA17869@ti88.telemetry-investments.com>

On Sat, 2007-05-19 at 14:55 -0400, Bill Rugolsky Jr. wrote:
> On Fri, May 18, 2007 at 11:14:57PM +0200, Krzysztof Halasa wrote:
> > I'm certainly missing something but what are the advantages of this
> > code (over current gzip etc.), and what will be using it?
> 
> Richard's patchset added it to the crypto library and wired it into
> the JFFS2 file system. 

Basically, LZO has much faster decompression speeds. For jffs2, there
was a 40% filesystem read speed improvement with LZO compared to zlib
and that resulted in a device booting 10% faster. The drawback was a
slight drop in file compression (say 5% although it varied a lot
depending on the test data). For lots of uses, that is an acceptable
compromise.

It appears resier4 is using LZO too.

> We recently started using LZO in a userland UDP
> proxy to do stateless per-packet payload compression over a WAN link.
> With ~1000 octet packets, our particular data stream sees 60% compression
> with zlib, and 50% compression with (mini-)LZO, but LZO runs at ~5.6x
> the speed of zlib.  IIRC, that translates into > 700Mbps on the input
> side on a 2GHZ Opteron, without any further tuning.

Those figures sound comparable with my experiences...

Richard



  reply	other threads:[~2007-05-19 21:52 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-18  9:58 [RFC] LZO1X de/compression support Nitin Gupta
2007-05-18 10:14 ` Heikki Orsila
2007-05-18 11:27   ` Nitin Gupta
2007-05-18 11:53     ` Richard Purdie
2007-05-18 10:42 ` Pekka Enberg
2007-05-18 10:53   ` Pekka Enberg
2007-05-22  8:54   ` Nitin Gupta
2007-05-22  8:59     ` Pekka Enberg
2007-05-22  9:10       ` Nitin Gupta
2007-05-22  9:34         ` Pekka Enberg
2007-05-18 11:11 ` Andrey Panin
2007-05-22  9:08   ` Nitin Gupta
2007-05-22 19:44     ` Jan Engelhardt
2007-05-22 21:24     ` Bernd Petrovitsch
2007-05-23 16:35       ` Jeremy Fitzhardinge
2007-05-18 11:46 ` Richard Purdie
2007-05-22  9:19   ` Nitin Gupta
2007-05-18 20:04 ` Matt Mackall
2007-05-18 21:14 ` Krzysztof Halasa
2007-05-19 18:55   ` Bill Rugolsky Jr.
2007-05-19 21:52     ` Richard Purdie [this message]
2007-05-22 19:40 ` Jan Engelhardt
  -- strict thread matches above, loose matches on Subject: below --
2007-05-19 18:12 devzero
2007-05-20 11:42 Tomasz Chmielewski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1179611532.5852.25.camel@localhost.localdomain \
    --to=richard@openedhand.com \
    --cc=brugolsky@telemetry-investments.com \
    --cc=khc@pm.waw.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nitingupta910@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).