From: Merlin Moncure <mmoncure@gmail.com>
To: david@lang.hm
Cc: Greg Smith <gsmith@gregsmith.com>
Cc: Guillaume Cottenceau <gc@mnc.ch>
Cc: pgsql-performance@postgresql.org
Subject: Re: Choosing a filesystem
Date: Sun, 14 Sep 2008 22:49:14 -0400
Message-ID: <b42b73150809141949w6f07b3afu16c950dcf7b54c50@mail.gmail.com> (raw)
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>
On Sat, Sep 13, 2008 at 5:26 PM, <david@lang.hm> wrote:
> On Fri, 12 Sep 2008, Merlin Moncure wrote:
>>
>> 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.
The heap files have to be synced as well during checkpoints, etc.
merlin
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: mmoncure@gmail.com, david@lang.hm, gsmith@gregsmith.com, gc@mnc.ch
Subject: Re: Choosing a filesystem
In-Reply-To: <b42b73150809141949w6f07b3afu16c950dcf7b54c50@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> <alpine.DEB.1.10.0809131423570.17867@asgard.lang.hm> <b42b73150809141949w6f07b3afu16c950dcf7b54c50@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