Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 89B439FB394 for ; Wed, 11 Jul 2007 15:45:10 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 88321-01 for ; Wed, 11 Jul 2007 15:45:01 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from beaver.fastcrypt.com (beaver.fastcrypt.com [64.7.141.17]) by postgresql.org (Postfix) with ESMTP id 0717E9FA377 for ; Wed, 11 Jul 2007 15:45:02 -0300 (ADT) Received: from [192.168.1.14] (dcdsl.ebox.com [64.7.143.116]) by beaver.fastcrypt.com (Postfix) with ESMTP id B40D91580683; Wed, 11 Jul 2007 14:58:39 -0400 (EDT) In-Reply-To: References: <877ip7avda.fsf@oxford.xeocode.com> <0DA358AF-4CF3-4910-8E48-26403AE8C0AC@fastcrypt.com> <60zm22x2jo.fsf@dba2.int.libertyrms.com> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Cc: pgsql-performance@postgresql.org Content-Transfer-Encoding: 7bit From: Dave Cramer Subject: Re: best use of an EMC SAN Date: Wed, 11 Jul 2007 14:45:06 -0400 To: Greg Smith X-Mailer: Apple Mail (2.752.3) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200707/112 X-Sequence-Number: 25796 On 11-Jul-07, at 2:35 PM, Greg Smith wrote: > On Wed, 11 Jul 2007, Jim Nasby wrote: > >> I suppose an entirely in-memory database might be able to swamp a >> 2 drive WAL as well. > > You can really generate a whole lot of WAL volume on an EMC SAN if > you're doing UPDATEs fast enough on data that is mostly in-memory. > Takes a fairly specific type of application to do that though, and > whether you'll ever find it outside of a benchmark is hard to say. > Well, this is such an application. The db fits entirely in memory, and the site is doing over 12M page views a day (I'm not exactly sure what this translates to in transactions) . > The main thing I would add as a consideration here is that you can > configure PostgreSQL to write WAL data using the O_DIRECT path, > bypassing the OS buffer cache, and greatly improve performance into > SAN-grade hardware like this. That can be a big win if you're > doing writes that dirty lots of WAL, and the benefit is > straightforward to measure if the WAL is a dedicated section of > disk (just change the wal_sync_method and do benchmarks with each > setting). If the WAL is just another section on an array, how well > those synchronous writes will mesh with the rest of the activity on > the system is not as straightforward to predict. Having the WAL > split out provides a logical separation that makes figuring all > this out easier. > > Just to throw out a slightly different spin on the suggestions > going by here: consider keeping the WAL separate, starting as a > RAID-1 volume, but keep 2 disks in reserve so that you could easily > upgrade to a 0+1 set if you end up discovering you need to double > the write bandwidth. Since there's never much actual data on the > WAL disks that would a fairly short downtime operation. If you > don't reach a wall, the extra drives might serve as spares to help > mitigate concerns about the WAL drives burning out faster than > average because of their high write volume. > > -- > * Greg Smith gsmith@gregsmith.com http://www.gregsmith.com > Baltimore, MD > > ---------------------------(end of > broadcast)--------------------------- > TIP 3: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faq