pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alex Turner <armtuk@gmail.com>
To: Welty, Richard <richard.welty@bankofamerica.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: RAID Stripe size
Date: Tue, 20 Sep 2005 11:33:29 -0400
Message-ID: <33c6269f050920083334b131bc@mail.gmail.com> (raw)
In-Reply-To: <A209FE4DA934614CAF3F5BD8E5E14290B0DD8D@ex2k.bankofamerica.com>
References: <A209FE4DA934614CAF3F5BD8E5E14290B0DD8D@ex2k.bankofamerica.com>

I have found JFS to be just fine. We have been running a medium load on this 
server for 9 months with no unscheduled down time. Datbase is about 30gig on 
disk, and we get about 3-4 requests per second that generate results sets in 
the thousands from about 8am to about 11pm.

I have foudn that JFS barfs if you put a million files in a directory and 
try to do an 'ls', but then so did reiser, only Ext3 handled this test 
succesfully. Fortunately with a database, this is an atypical situation, so 
JFS has been fine for DB for us so far.

We have had severe problems with Ext3 when file systems hit 100% usage, they 
get all kinds of unhappy, we haven't had the same problem with JFS.

Alex Turner
NetEconomist

On 9/20/05, Welty, Richard <richard.welty@bankofamerica.com> wrote:
> 
> Alex Turner wrote:
> 
> > I would also recommend looking at file system. For us JFS worked 
> signifcantly
> > faster than resier for large read loads and large write loads, so we 
> chose JFS
> > over ext3 and reiser.
> 
> has jfs been reliable for you? there seems to be a lot of conjecture about 
> instability,
> but i find jfs a potentially attractive alternative for a number of 
> reasons.
> 
> richard
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
>

view thread (10+ messages)  latest in thread

Message-ID: <33c6269f050920083334b131bc@mail.gmail.com>
Permalink:  ../33c6269f050920083334b131bc@mail.gmail.com/
Also on:    postgresql.org/message-id/33c6269f050920083334b131bc@mail.gmail.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: armtuk@gmail.com, richard.welty@bankofamerica.com
  Subject: Re: RAID Stripe size
  In-Reply-To: <33c6269f050920083334b131bc@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