All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gregory Maxwell <gmaxwell@gmail.com>
To: David Masover <ninja@slaphack.com>,
	ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: reiser4 performance
Date: Mon, 8 Aug 2005 20:58:45 -0400	[thread overview]
Message-ID: <e692861c050808175818078a30@mail.gmail.com> (raw)
In-Reply-To: <42F7F6DC.2080706@slaphack.com>

On 8/8/05, David Masover <ninja@slaphack.com> wrote:
> 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

Given webserver horsepower from the same budget class as the Internet
pipe it is attached to, it is utterly trivial to saturate the pipe
with static content.. even if the files are small, larger than core in
total, and have poor locality.   (and those are very infrequently the
case).

So for most webserver cases, FS speed doesn't matter. For the few
cases where it does, locality is usually fairly good... so who cares
if the new FS is 2x faster, when it is still 200x slower than ram. Add
ram.

> mailserver -- especially IMAP+maildir, lots of small files, read/write
> and so on...

An interesting application space, no doubt. Although you can cure a
lot of sins tossing solid state disk at it. :) (or just battery backed
cache on a hardware raid controller).

> 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
[snip]

Rsync algo or the network is going to be your bottleneck there, for
the sync... Are you really getting disk bound for compile? if so
increase your -j N.


> 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.

I agree. Still it would be nice to have some really good bread and
butter improvements.. and a sufficient level of 'transaction' support
exposed to PostgreSQL could result in a huge performance improvement
while improving reliability. "Your database is more reliable on
reiser4" would be a compelling argument... even to those not convinced
by plugins and small files.

  reply	other threads:[~2005-08-09  0:58 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
2005-08-09  0:58       ` Gregory Maxwell [this message]
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=e692861c050808175818078a30@mail.gmail.com \
    --to=gmaxwell@gmail.com \
    --cc=ninja@slaphack.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.