From: Scott Marlowe <scott.marlowe@gmail.com>
To: Trevor Talbot <quension@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Performance on 8CPU's and 32GB of RAM
Date: Wed, 5 Sep 2007 14:29:25 -0500
Message-ID: <dcc563d10709051229q28767cbtc61a5af11447faa5@mail.gmail.com> (raw)
In-Reply-To: <90bce5730709051016j5291827dx525d6b8fe4960fbd@mail.gmail.com>
References: <fbkn5d$cfq$1@news.hub.org>
<20070904230639.GA23731@alvh.no-ip.org>
<dcc563d10709041615s305ae98bm92dee61ab199b7c4@mail.gmail.com>
<46DE66CF.9000903@theendofthetunnel.de>
<fbmhjt$d51$1@news.hub.org>
<dcc563d10709050845k135d3c2erbe5b44933e898aa@mail.gmail.com>
<90bce5730709051016j5291827dx525d6b8fe4960fbd@mail.gmail.com>
On 9/5/07, Trevor Talbot <quension@gmail.com> wrote:
> On 9/5/07, Scott Marlowe <scott.marlowe@gmail.com> wrote:
> > On 9/5/07, Carlo Stonebanks <stonec.register@sympatico.ca> wrote:
> > > > Right, additionally NTFS is really nothing to use on any serious disc
> > > > array.
> > >
> > > Do you mean that I will not see any big improvement if I upgrade the disk
> > > subsystem because the client is using NTFS (i.e. Windows)
> >
> > No, I think he's referring more to the lack of reliability of NTFS
> > compared to UFS / ZFS / JFS / XFS on unixen.
>
> Lack of reliability compared to _UFS_? Can you elaborate on this?
Not a lot. Back when I was an NT 4.0 sysadmin, I had many many
occasions where NTFS simply corrupted for no apparent reason. No
system crash, no obvious problems with the drive, and bang suddenly a
file goes corrupted. About that time I gave up on Windows and started
supporting Linux and Solaris. Neither is perfect, but I've never had
either of them just corrupt a file on good hardware for no reason.
Keep in mind, the machine that was corrupting files for no reason went
on to be our development / staging linux server, handling quite a
heavy load of developers on it, and never once had a corrupted file on
it.
With the newer journalling file systems on linux, solaris and BSD, you
get both good performance and very reliable behaviour. Maybe NTFS has
gotten better since then, but I don't personally know.
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: scott.marlowe@gmail.com, quension@gmail.com
Subject: Re: Performance on 8CPU's and 32GB of RAM
In-Reply-To: <dcc563d10709051229q28767cbtc61a5af11447faa5@mail.gmail.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