From: Hans Reiser <reiser@namesys.com>
To: PFC <lists@peufeu.com>
Cc: "reiserfs-list@namesys.com" <reiserfs-list@namesys.com>
Subject: Re: Reiser4 und LZO compression
Date: Tue, 29 Aug 2006 10:56:59 -0700 [thread overview]
Message-ID: <44F47FEB.9060005@namesys.com> (raw)
In-Reply-To: <op.te1yjbp7cigqcu@apollo13>
PFC, thanks for giving us some real data. May I post it to the lkml thread?
In essence, LZO wins the benchmarks, and the code is hard to read. I
guess I have to go with LZO, and encourage people to take a stab at
dethroning it.
Hans
PFC wrote:
>
> I have made a little openoffice spreadsheet with the results.
> You can have fun entering stuff and seeing the results.
>
> http://peufeu.free.fr/compression.ods
>
> Basically, a laptop having the same processor as my PC and a
> crummy 15 MB/s drive (like most laptop drives) will get a 2.5x speedup
> using lzf, while using 40% CPU for compression and 15% CPU for
> decompression. I'd say it's a clear, huuuuge win.
>
> A desktop computer with a modern IDE drive doing 50 MB/s will
> still get nice speedups (1.8x on write, 2.5x on read) but of course,
> more CPU will be used because of the higher throughput. In this case
> it is CPU limited on compression and disk limited on decompression.
> However soon everyone will have dual core monsters so...
>
> A big ass RAID will not get much benefit unless :
> - the buffer cache stores compressed pages, so compression
> virtually doubles the RAM cache
> - or the CPU is really fast
> - or you put one of these neat FPGA modules in a free Opteron
> socket and upload a soft-hardware LZF in it with a few gigabytes/s
> throughput
Or you look the sysadmin in the eyes, and say, your file servers have
more out of disk space problems than load problems, yes?
>
> ...
>
>
next prev parent reply other threads:[~2006-08-29 17:56 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-27 0:34 Reiser4 und LZO compression Alexey Dobriyan
2006-08-27 8:04 ` Andrew Morton
2006-08-27 8:49 ` Ray Lee
2006-08-27 9:42 ` David Masover
2006-08-28 17:34 ` Jindrich Makovicka
2006-08-28 18:05 ` Edward Shishkin
2006-08-28 12:42 ` Jörn Engel
2006-08-29 13:14 ` PFC
2006-08-29 17:38 ` David Masover
2006-08-28 17:06 ` Hans Reiser
2006-08-28 17:37 ` Stefan Traby
2006-08-28 18:15 ` Edward Shishkin
2006-08-28 21:48 ` Nigel Cunningham
2006-08-28 23:32 ` Hans Reiser
2006-08-29 4:05 ` Jan Engelhardt
2006-08-29 5:41 ` Nigel Cunningham
2006-08-29 8:23 ` David Masover
2006-08-29 9:57 ` Nigel Cunningham
2006-08-29 11:09 ` Ray Lee
2006-08-29 11:38 ` Edward Shishkin
2006-08-29 22:03 ` Nigel Cunningham
2006-08-29 4:59 ` Paul Mundt
2006-08-29 5:47 ` Nigel Cunningham
2006-08-29 13:45 ` PFC
2006-08-29 14:38 ` Stefan Traby
2006-08-29 15:55 ` PFC
2006-08-29 17:56 ` Hans Reiser [this message]
2006-08-29 18:31 ` David Masover
2006-08-29 18:36 ` Gregory Maxwell
2006-08-29 19:11 ` David Masover
2006-08-29 19:38 ` Hans Reiser
2006-08-29 20:03 ` David Masover
2006-08-29 22:15 ` Toby Thain
2006-08-29 22:42 ` David Masover
2006-08-30 9:17 ` PFC
2006-08-30 10:45 ` David Masover
2006-08-30 16:50 ` Edward Shishkin
2006-08-30 16:55 ` Hans Reiser
2006-08-31 9:32 ` Clemens Eisserer
2006-08-31 12:00 ` Edward Shishkin
2006-08-31 15:14 ` Clemens Eisserer
2006-08-31 16:55 ` Hans Reiser
2006-08-31 18:08 ` Edward Shishkin
2006-08-31 19:22 ` David Masover
2006-08-29 15:41 ` Gregory Maxwell
2006-08-29 17:42 ` Hans Reiser
2006-08-29 9:29 ` Edward Shishkin
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=44F47FEB.9060005@namesys.com \
--to=reiser@namesys.com \
--cc=lists@peufeu.com \
--cc=reiserfs-list@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.