From: Paul Jackson <pj@sgi.com>
To: root@chaos.analogic.com
Cc: joelja@darkwing.uoregon.edu, miller@techsource.com,
tytso@mit.edu, miquels@cistron.nl, linux-kernel@vger.kernel.org
Subject: Re: File system compression, not at the block layer
Date: Fri, 23 Apr 2004 16:34:20 -0700 [thread overview]
Message-ID: <20040423163420.43f55a90.pj@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0404231624010.1352@chaos>
> If you want to have fast disks, then you should do what I
> suggested to Digital 20 years ago when they had ST-506
> interfaces and SCSI was available only from third-parties.
> It was called "striping" (I'm serious!).
That gets your bandwidth up, but does nothing for latency.
Depending on your workload, that may or may not be critical.
As a former SGI employee noted:
"Money can buy bandwidth, but latency is forever" -- John Mashey
To get latency down, you need fast rotating disks and short strokes
(waste most of the disk on little used data, or on nothing at all).
And even that won't get you much faster than 20 years ago.
That, or lots of main memory, or if the data is pretty much
read-only, perhaps some complicated data duplication.
But we're not in such bad shape there - folks have been dealing
with that speed difference for at least 20 years ;).
It's the speed difference between the processor and main memory
that's more challenging now - as it approaches speed differences
we once saw between processor and disk.
To heck with disk compression - it's time for main memory compression.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373
next prev parent reply other threads:[~2004-04-23 23:36 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-23 17:26 File system compression, not at the block layer Timothy Miller
2004-04-23 17:30 ` Miquel van Smoorenburg
2004-04-23 17:41 ` Theodore Ts'o
2004-04-23 17:57 ` Jörn Engel
2004-04-23 18:14 ` Timothy Miller
2004-04-23 18:34 ` Paul Jackson
2004-04-23 20:14 ` Joel Jaeggli
2004-04-23 20:34 ` Richard B. Johnson
2004-04-23 20:44 ` Måns Rullgård
2004-04-23 20:59 ` Richard B. Johnson
2004-04-23 21:14 ` Ben Greear
2004-04-23 21:25 ` Timothy Miller
2004-04-24 4:58 ` Ben Greear
2004-04-27 15:45 ` Timothy Miller
2004-04-23 21:18 ` Timothy Miller
2004-04-24 1:28 ` Horst von Brand
2004-04-24 2:24 ` Tom Vier
2004-04-24 7:36 ` Willy Tarreau
2004-04-24 16:02 ` Eric D. Mudama
2004-04-25 3:05 ` Horst von Brand
2004-04-25 7:29 ` Willy Tarreau
2004-04-25 19:50 ` Eric D. Mudama
2004-04-27 15:43 ` Timothy Miller
2004-04-28 0:29 ` Tom Vier
2004-04-23 21:31 ` Joel Jaeggli
2004-04-23 22:20 ` Ian Stirling
2004-04-23 23:34 ` Paul Jackson [this message]
2004-04-27 15:42 ` Timothy Miller
2004-04-27 16:02 ` Jörn Engel
2004-04-24 1:18 ` Horst von Brand
2004-04-26 10:22 ` Jörn Engel
2004-04-23 21:15 ` Timothy Miller
2004-04-23 21:36 ` Joel Jaeggli
2004-04-27 20:34 ` Pavel Machek
2004-04-28 22:57 ` Timothy Miller
2004-04-29 9:46 ` Jörn Engel
2004-04-29 9:52 ` Pavel Machek
2004-04-29 10:09 ` Jörn Engel
2004-04-29 10:19 ` Pavel Machek
2004-04-29 17:17 ` Tim Connors
2004-04-28 1:00 ` David Lang
2004-04-28 10:09 ` Jörn Engel
2004-04-28 10:21 ` Nikita Danilov
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=20040423163420.43f55a90.pj@sgi.com \
--to=pj@sgi.com \
--cc=joelja@darkwing.uoregon.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=miller@techsource.com \
--cc=miquels@cistron.nl \
--cc=root@chaos.analogic.com \
--cc=tytso@mit.edu \
/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