From: Krzysztof Halasa <khc@pm.waw.pl>
To: johnrobertbanks@fastmail.fm
Cc: "Jan Harkes" <jaharkes@cs.cmu.edu>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: Reiser4. BEST FILESYSTEM EVER.
Date: Sat, 07 Apr 2007 16:11:46 +0200 [thread overview]
Message-ID: <m34pns46l9.fsf@maximus.localdomain> (raw)
In-Reply-To: <1175925525.21154.1183436614@webmail.messagingengine.com> (johnrobertbanks@fastmail.fm's message of "Fri, 06 Apr 2007 22:58:45 -0700")
johnrobertbanks@fastmail.fm writes:
> Why do you think I hate reiserfs developers? That is an insane claim.
> Why would I hate reiser3 developers?
> Why would I hate reiser4 developers?
> Why would I even dislike them?
>
> I think Hans Reiser is a genius. Is that what you mean by hate?
I think they could hire a person with a bit better marketing skills,
though. People on a technical mailing list don't buy things just
because something on TV told them they have to.
> Answer this question. Why do YOU think I am antagonizing reiserfs
> developers?
That might be just a side effect.
> Think about it,... read speeds that are some FOUR times the physical
> disk read rate,... impossible without the use of compression (or
> something similar).
It's really impossible with compression only unless you're writing
only zeros or stuff alike. I don't know what bonnie uses for testing
but real life data doesn't compress 4 times. Two times, sometimes,
but then it will be typically slower than disk access (I mean read,
as write will be much slower).
You can get faster I/O (both linear speed and access times) using
multiple disks (mirrors etc). Perhaps some ZFS ideas would do us
some good?
Gzip - 3 files (zeros only, raw DV data from video camera, x86_64
kernel rpm file), 10 MB of data (10*1024*1024), done on tmpfs so no
real disk speed factor. The CPU is AMD64 with 1 MB cache per core,
2600 MHz clock (clock scaling disabled). That's my typical usage
pattern (well, not counting these zeros).
$ l -Ggh zeros dv bin
-rw-r--r-- 1 10M Apr 7 15:30 bin
-rw-r--r-- 1 10M Apr 7 15:31 dv
-rw-r--r-- 1 10M Apr 7 15:31 zeros
$ for f in zeros dv bin; do time gzip $f; done
real 0m0.112s
real 0m0.686s
real 0m0.559s
Dealing with pure zeros gzip can get almost 90 MB/s compressing, but
with DV and rpm it only does 14.5 and almost 18 MB/s respectively...
$ l -Ggh zeros.gz dv.gz bin.gz
-rw-r--r-- 1 10K Apr 7 15:31 zeros.gz
-rw-r--r-- 1 9.1M Apr 7 15:31 dv.gz
-rw-r--r-- 1 9.3M Apr 7 15:30 bin.gz
... and though the numbers may still sound impressive, space savings
are less than 10%.
$ for f in zeros dv bin; do time gunzip $f.gz; done
real 0m0.067s
real 0m0.131s
real 0m0.120s
Decompression gives 150 MB/s for zeros and ~ 80 MB/s for DV and rpm.
$ for f in zeros dv bin; do time gzip -1 $f; done
real 0m0.079s
real 0m0.572s
real 0m0.530s
Supposed to be "fastest gzip". 126 MB/s for zeros but still less than
19 MB/s for DV and rpm.
$ l -Ggh zeros.gz dv.gz bin.gz
-rw-r--r-- 1 45K Apr 7 15:31 zeros.gz
-rw-r--r-- 1 9.2M Apr 7 15:31 dv.gz
-rw-r--r-- 1 9.3M Apr 7 15:30 bin.gz
$ for f in zeros dv bin; do time gunzip $f.gz; done
real 0m0.044s
real 0m0.135s
real 0m0.120s
It seems gzip can decompress zeros with 227 MB/s rate.
I assume the "4x read speed" claim comes from something like this.
$ /sbin/hdparm -t /dev/sda
/dev/sda:
Timing buffered disk reads: 210 MB in 3.02 seconds = 69.59 MB/sec
$ echo "69.59*4" | bc
278.36
Seems you'd need a faster algorithm, faster machine or slower disk
- slower than this cheap SATA with disabled NCQ (NV SATA) at least:
$ cat /sys/block/sda/device/model
Maxtor 6V250F0
Please note that aplication-level compression usually gives way
better results - the application knows much more.
--
Krzysztof Halasa
next prev parent reply other threads:[~2007-04-07 14:11 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 22:42 REISER4: fix for reiser4_write_extent Ignatich
2007-04-06 0:05 ` Reiser4. BEST FILESYSTEM EVER? I need help johnrobertbanks
2007-04-06 0:23 ` H. Peter Anvin
2007-04-06 0:34 ` johnrobertbanks
2007-04-06 0:39 ` H. Peter Anvin
2007-04-06 1:34 ` Reiser4. BEST FILESYSTEM EVER johnrobertbanks
2007-04-06 3:12 ` Valdis.Kletnieks
2007-04-06 4:07 ` H. Peter Anvin
2007-04-06 4:32 ` johnrobertbanks
[not found] ` <20070406152119.GC4228@delft.aura.cs.cmu.edu>
2007-04-07 2:47 ` johnrobertbanks
2007-04-07 3:30 ` Jan Harkes
2007-04-07 5:58 ` johnrobertbanks
2007-04-07 7:15 ` Willy Tarreau
2007-04-07 13:47 ` johnrobertbanks
2007-04-07 14:11 ` Krzysztof Halasa [this message]
2007-04-07 15:07 ` johnrobertbanks
2007-04-07 16:05 ` Pekka Enberg
2007-04-07 17:10 ` Valdis.Kletnieks
2007-04-08 16:31 ` Adrian Bunk
2007-04-07 17:21 ` Valdis.Kletnieks
2007-04-08 0:41 ` Krzysztof Halasa
2007-04-07 17:39 ` Valdis.Kletnieks
2007-04-07 19:17 ` Lennart Sorensen
2007-04-08 0:44 ` johnrobertbanks
2007-04-08 1:27 ` Lennart Sorensen
2007-04-08 2:56 ` Theodore Tso
2007-04-08 4:13 ` johnrobertbanks
2007-04-08 12:48 ` Jose Celestino
2007-04-08 13:21 ` johnrobertbanks
2007-04-08 14:14 ` Willy Tarreau
2007-04-08 17:03 ` Theodore Tso
2007-04-08 18:18 ` Jeff Mahoney
2007-04-08 4:32 ` Christer Weinigel
2007-04-08 21:50 ` Reiser4. BEST FILESYSTEM EVER - Christer Weinigel johnrobertbanks
2007-04-08 22:58 ` Richard Knutsson
2007-04-09 5:14 ` johnrobertbanks
2007-04-09 7:07 ` Willy Tarreau
2007-04-09 16:10 ` Richard Knutsson
2007-04-09 18:35 ` Reiser4. BEST FILESYSTEM EVER Nate Diller
2007-04-07 1:26 ` COMPILING AND CONFIGURING A NEW KERNEL johnrobertbanks
2007-04-07 7:45 ` johnrobertbanks
2007-04-07 16:57 ` Valdis.Kletnieks
2007-04-08 1:11 ` johnrobertbanks
2007-04-07 16:42 ` Valdis.Kletnieks
2007-04-08 1:02 ` johnrobertbanks
2007-04-08 1:42 ` Lennart Sorensen
2007-04-07 12:51 ` REISER4: fix for reiser4_write_extent Laurent Riffard
2007-04-07 19:29 ` Edward Shishkin
2007-04-07 12:59 Reiser4. BEST FILESYSTEM EVER Dale Amon
2007-04-07 15:28 ` johnrobertbanks
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=m34pns46l9.fsf@maximus.localdomain \
--to=khc@pm.waw.pl \
--cc=jaharkes@cs.cmu.edu \
--cc=johnrobertbanks@fastmail.fm \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®