pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Christopher Browne <cbbrowne@acm.org>
To: pgsql-performance@postgresql.org
Subject: Re: fsync vs open_sync
Date: Sat, 04 Sep 2004 23:47:55 -0400
Message-ID: <m3r7ph2x78.fsf@wolfe.cbbrowne.com> (raw)
References: <6EE64EF3AB31D5448D0007DD34EEB3412A749A@Herge.rcsinc.local>

The world rejoiced as merlin.moncure@rcsonline.com ("Merlin Moncure") wrote:
> Ok, you were right.  I made some tests and NTFS is just not very
> good in the general case.  I've seen some benchmarks for Reiser4
> that are just amazing.

Reiser4 has been sounding real interesting.

The killer problem is thus:

  "We must caution that just as Linux 2.6 is not yet as stable as
  Linux 2.4, it will also be some substantial time before V4 is as
  stable as V3."

In practice, there's a further problem.

We have some systems at work we need to connect to EMC disk arrays;
that's something that isn't supported by EMC unless you're using a
whole set of pieces that are "officially supported."

RHAT doesn't want to talk to you about support for anything other than
ext3.

I'm not sure what all SuSE supports; they're about the only other Linx
vendor that EMC would support, and I don't expect that Reiser4 yet
fits into the "supportable" category :-(.

The upshot of that is that this means that we'd only consider using
stuff like Reiser4 on "toy" systems, and, quite frankly, that means
that they'll have "toy" disk as opposed to the good stuff :-(.

And frankly, we're too busy with issues nearer to our hearts than
testing out ReiserFS.  :-(
-- 
output = ("cbbrowne" "@" "cbbrowne.com")
http://cbbrowne.com/info/emacs.html
"Linux!  Guerrilla Unix Development     Venimus, Vidimus, Dolavimus."
-- <mah@ka4ybr.com> Mark A. Horton KA4YBR



view thread (20+ messages)  latest in thread

Message-ID: <m3r7ph2x78.fsf@wolfe.cbbrowne.com>
Permalink:  ../m3r7ph2x78.fsf@wolfe.cbbrowne.com/
Also on:    postgresql.org/message-id/m3r7ph2x78.fsf@wolfe.cbbrowne.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: cbbrowne@acm.org
  Subject: Re: fsync vs open_sync
  In-Reply-To: <m3r7ph2x78.fsf@wolfe.cbbrowne.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox