From: David Masover <ninja@slaphack.com>
To: Gregory Maxwell <gmaxwell@gmail.com>
Cc: Hans Reiser <reiser@namesys.com>,
ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: reiser4 performance
Date: Mon, 08 Aug 2005 19:20:44 -0500 [thread overview]
Message-ID: <42F7F6DC.2080706@slaphack.com> (raw)
In-Reply-To: <e692861c05080816136f9d70bc@mail.gmail.com>
Gregory Maxwell wrote:
> On 8/8/05, Hans Reiser <reiser@namesys.com> wrote:
> If ever you are looking for a killer app for Reiser4 that people who
> don't care about the visionary stuff will care about:
Define "visionary"?
I can name a few things that work best in Reiser4, and very well in v3,
simply because of efficient storage of small files and lazy allocation:
webserver -- lots of small files, very few large ones, mostly reads
mailserver -- especially IMAP+maildir, lots of small files, read/write
and so on...
Gentoo box:
/usr/portage is over a hundred thousand very small files, updated via
rsync. Since they are updated all at once, you get a boost out of lazy
allocation -- you only touch the disks for reads while you're talking to
the server, because most of the writes probably won't hit the disk for
awhile.
/var/tmp/portage is what Portage uses for compilation. A source
tarball (usually a tarball, can be anything) is unpacked from
/usr/portage/distfiles into /var/tmp/portage/<package>/build. It's
compiled, then installed into /var/tmp/portage/<package>/install, then
Portage manually merges the /install directory with the main filesystem,
in one operation -- presumably so that it could become atomic someday.
After the merge, /var/tmp/portage is cleaned for the next package.
With enough RAM, most of the contents (source code and object files)
from /var/tmp/portage would never touch disk. This becomes an
especially huge win if your /var/tmp/portage is a separate partition --
instead of writing (unpack tarball), then reading, then writing again
(for install/merge), you write once. What was a 5, 6, or 7-step process
is now a 1-step process. And, if you don't have enough RAM for this
RAM-disk-like behavior, it falls back to the old way.
These are all things that Reiser4 already does better than anything
else. So now we're going to get Postgres to run faster. I can't wait
until we have more people hacking on the plugin interface -- then we'll
have some *real* killer apps.
next prev parent reply other threads:[~2005-08-09 0:20 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 10:32 reiser4 performance Hemiplegic Menehune
2005-08-08 10:51 ` PFC
2005-08-08 11:09 ` Raymond A. Meijer
2005-08-08 13:38 ` Ingo Bormuth
2005-08-08 16:44 ` PFC
2005-08-08 19:53 ` David Masover
2005-08-08 20:30 ` michael chang
2005-08-08 20:34 ` michael chang
2005-08-08 20:40 ` Bedros Hanounik
2005-08-08 20:58 ` michael chang
2005-08-08 21:41 ` Ingo Bormuth
2005-08-08 20:51 ` Funding [Was:reiser4 performance] Pysiak Satriani
2005-08-08 19:56 ` reiser4 performance David Masover
2005-08-08 22:06 ` Hans Reiser
2005-08-09 0:02 ` David Masover
2005-08-09 0:16 ` michael chang
2005-08-09 1:02 ` David Masover
2005-08-09 17:52 ` michael chang
2005-08-09 20:19 ` Valdis.Kletnieks
2005-08-10 1:23 ` David Masover
2005-08-10 21:33 ` Hans Reiser
2005-08-08 18:09 ` Hans Reiser
2005-08-08 18:10 ` Hans Reiser
2005-08-08 23:13 ` Gregory Maxwell
2005-08-08 23:30 ` Hans Reiser
2005-08-09 0:20 ` David Masover [this message]
2005-08-09 0:58 ` Gregory Maxwell
2005-08-09 1:33 ` David Masover
2005-08-09 1:55 ` Gregory Maxwell
2005-08-11 18:49 ` Hans Reiser
2005-08-11 19:00 ` PFC
2005-08-11 21:29 ` Gregory Maxwell
2005-08-09 2:03 ` Gregory Maxwell
2005-08-10 1:34 ` David Masover
2005-08-10 1:51 ` Pat Double
2005-08-10 2:11 ` David Masover
2005-08-10 2:19 ` Pat Double
2005-08-10 2:32 ` David Masover
2005-08-10 2:49 ` Pat Double
2005-08-09 7:41 ` PFC
-- strict thread matches above, loose matches on Subject: below --
2005-08-08 20:57 Pysiak Satriani
2005-08-08 22:42 ` Hans Reiser
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=42F7F6DC.2080706@slaphack.com \
--to=ninja@slaphack.com \
--cc=gmaxwell@gmail.com \
--cc=reiser@namesys.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.