From: Gregory Maxwell <gmaxwell@gmail.com>
To: Hans Reiser <reiser@namesys.com>,
ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: reiser4 performance
Date: Mon, 8 Aug 2005 19:13:20 -0400 [thread overview]
Message-ID: <e692861c05080816136f9d70bc@mail.gmail.com> (raw)
In-Reply-To: <42F7A01A.7090209@namesys.com>
On 8/8/05, Hans Reiser <reiser@namesys.com> wrote:
> I should add that fsync performance has not been worked on yet, which is
> surely why postgres performance is poor.
Hans, I'm on the postgresql hackers list (although I don't really have
a voice there, so I can't really speak much for reiser4 there)..
One of the 'interesting' issues they face is that that postgresql
database works with 8K pages. From a performance and reliability
perspective they would benefit impressively from a file system (and
VFS) which could atomically update their 8k pages. Without such a
feature their performance is slaughtered when operating in a mode that
provides the highest reliability, and their reliability is slaughtered
when operating in the highest performance configuration.
I'm sure the PostgreSQL folks would be here themselves asking for help
with this issue... if they weren't so oriented around FreeBSD. :)
If ever you are looking for a killer app for Reiser4 that people who
don't care about the visionary stuff will care about: you couldn't
find one better than postgresql. If you could get postgresql working
as reliably as a double logged full fsync configuration but performing
as fast as a configuration with async writes.... you'd have a lot more
supporters.
next prev parent reply other threads:[~2005-08-08 23:13 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 [this message]
2005-08-08 23:30 ` Hans Reiser
2005-08-09 0:20 ` David Masover
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=e692861c05080816136f9d70bc@mail.gmail.com \
--to=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.