pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: david@lang.hm
To: Merlin Moncure <mmoncure@gmail.com>
Cc: Greg Smith <gsmith@gregsmith.com>
Cc: Guillaume Cottenceau <gc@mnc.ch>
Cc: pgsql-performance@postgresql.org
Subject: Re: Choosing a filesystem
Date: Sat, 13 Sep 2008 14:26:40 -0700 (PDT)
Message-ID: <alpine.DEB.1.10.0809131423570.17867@asgard.lang.hm> (raw)
In-Reply-To: <b42b73150809120735r663d8687had9da4b1a936cbe5@mail.gmail.com>
References: <48C94770.2090505@shopzeus.com>
	<alpine.DEB.1.10.0809111814130.4454@aragorn.flymine.org>
	<20080911172332.GP6714@it.is.rice.edu>
	<48C90F58.EE98.0025.0@wicourts.gov>
	<48C959BD.80307@shopzeus.com>
	<48C97740.9040404@emolecules.com>
	<873ak5iwru.fsf@mnc.ch>
	<Pine.GSO.4.64.0809120450430.6489@westnet.com>
	<b42b73150809120735r663d8687had9da4b1a936cbe5@mail.gmail.com>

On Fri, 12 Sep 2008, Merlin Moncure wrote:

> On Fri, Sep 12, 2008 at 5:11 AM, Greg Smith <gsmith@gregsmith.com> wrote:
>> On Fri, 12 Sep 2008, Guillaume Cottenceau wrote:
>>
>> That's the main thing, and nothing else you can do will accelerate that.
>> Without a useful write cache (which usually means RAM with a BBU), you'll at
>> best get about 100-200 write transactions per second for any one client, and
>> something like 500/second even with lots of clients (queued up transaction
>> fsyncs do get combined).  Those numbers increase to several thousand per
>> second the minute there's a good caching controller in the mix.
>
> While this is correct, if heavy writing is sustained, especially on
> large databases, you will eventually outrun the write cache on the
> controller and things will start to degrade towards the slow case.  So
> it's fairer to say that caching raid controllers burst up to several
> thousand per second, with a sustained write rate somewhat better than
> write-through but much worse than the burst rate.
>
> How fast things degrade from the burst rate depends on certain
> factors...how big the database is relative to the o/s read cache in
> the controller write cache, and how random the i/o is generally.  One
> thing raid controllers are great at is smoothing bursty i/o during
> checkpoints for example.
>
> Unfortunately when you outrun cache on raid controllers the behavior
> is not always very pleasant...in at least one case I've experienced
> (perc 5/i) when the cache fills up the card decides to clear it before
> continuing.  This means that if fsync is on, you get unpredictable
> random freezing pauses while the cache is clearing.

although for postgres the thing that you are doing the fsync on is the WAL 
log file. that is a single (usually) contiguous file. As such it is very 
efficiant to write large chunks of it. so while you will degrade from the 
battery-only mode, the fact that the controller can flush many requests 
worth of writes out to the WAL log at once while you fill the cache with 
them one at a time is still a significant win.

David Lang



view thread (19+ messages)  latest in thread

Message-ID: <alpine.DEB.1.10.0809131423570.17867@asgard.lang.hm>
Permalink:  ../alpine.DEB.1.10.0809131423570.17867@asgard.lang.hm/
Also on:    postgresql.org/message-id/alpine.DEB.1.10.0809131423570.17867@asgard.lang.hm

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: david@lang.hm, mmoncure@gmail.com, gsmith@gregsmith.com, gc@mnc.ch
  Subject: Re: Choosing a filesystem
  In-Reply-To: <alpine.DEB.1.10.0809131423570.17867@asgard.lang.hm>
  References: <48C94770.2090505@shopzeus.com> <alpine.DEB.1.10.0809111814130.4454@aragorn.flymine.org> <20080911172332.GP6714@it.is.rice.edu> <48C90F58.EE98.0025.0@wicourts.gov> <48C959BD.80307@shopzeus.com> <48C97740.9040404@emolecules.com> <873ak5iwru.fsf@mnc.ch> <Pine.GSO.4.64.0809120450430.6489@westnet.com> <b42b73150809120735r663d8687had9da4b1a936cbe5@mail.gmail.com> <alpine.DEB.1.10.0809131423570.17867@asgard.lang.hm>

* 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