Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 5132364FCD9 for ; Sat, 13 Sep 2008 18:25:58 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 15478-02 for ; Sat, 13 Sep 2008 18:25:55 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from bifrost.lang.hm (mail.lang.hm [64.81.33.126]) by postgresql.org (Postfix) with ESMTP id 207A064FCDE for ; Sat, 13 Sep 2008 18:25:54 -0300 (ADT) Received: from asgard.lang.hm (asgard.lang.hm [10.0.0.100]) by bifrost.lang.hm (8.13.4/8.13.4/Debian-3) with ESMTP id m8DLPjuD032263; Sat, 13 Sep 2008 14:25:45 -0700 Date: Sat, 13 Sep 2008 14:26:40 -0700 (PDT) From: david@lang.hm X-X-Sender: dlang@asgard.lang.hm To: Merlin Moncure cc: Greg Smith , Guillaume Cottenceau , pgsql-performance@postgresql.org Subject: Re: Choosing a filesystem In-Reply-To: Message-ID: References: <48C94770.2090505@shopzeus.com> <20080911172332.GP6714@it.is.rice.edu> <48C90F58.EE98.0025.0@wicourts.gov> <48C959BD.80307@shopzeus.com> <48C97740.9040404@emolecules.com> <873ak5iwru.fsf@mnc.ch> User-Agent: Alpine 1.10 (DEB 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200809/168 X-Sequence-Number: 31481 On Fri, 12 Sep 2008, Merlin Moncure wrote: > On Fri, Sep 12, 2008 at 5:11 AM, Greg Smith 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