Received: from localhost (unknown [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 9CC7A2E311D for ; Wed, 2 Jan 2008 13:06:22 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 31409-03 for ; Wed, 2 Jan 2008 13:06:12 -0400 (AST) Received: from main2.mycybernet.net (main2.mycybernet.net [209.222.63.140]) by postgresql.org (Postfix) with ESMTP id B2D082E02BF for ; Wed, 2 Jan 2008 13:06:12 -0400 (AST) Received: from 227-54-222-209.mycybernet.net ([209.222.54.227] helo=crankycanuck.ca) by main2.mycybernet.net with esmtp (Exim 4.62) (envelope-from ) id 1JA72X-0005Tv-4u for pgsql-admin@postgresql.org; Wed, 02 Jan 2008 12:06:01 -0500 Received: by crankycanuck.ca (Postfix, from userid 1000) id 5C8A150098; Wed, 2 Jan 2008 12:05:56 -0500 (EST) Date: Wed, 2 Jan 2008 12:05:56 -0500 From: Andrew Sullivan To: pgsql-admin@postgresql.org Subject: Re: reconfiguring diskspace while upgrading to 8.2.5 Message-ID: <20080102170556.GA22706@crankycanuck.ca> Mail-Followup-To: Andrew Sullivan , pgsql-admin@postgresql.org References: <002901c84d50$d4841ed0$14010a0a@dei26g028575> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <002901c84d50$d4841ed0$14010a0a@dei26g028575> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/23 X-Sequence-Number: 27797 On Wed, Jan 02, 2008 at 10:04:53AM -0500, Mark Steben wrote: > The choices we see are: [. . .] I think this is likely to depend almost entirely on benchmarking your case, and testing the different possibilities. That said, except in extremely well-defined cases, it's often not a bad idea to make one large RAID anyway, because you sometimes find that your assumptions about your access patterns were wrong, and you've optimised for the wrong thing. In that case, the single large RAID offers greater flexibility, and if your controller is smart enough, the advantages are small enough that you don't gain enough for the loss in flexibility. I also want to point out that you need to test your workload _on 8.2_, and not make assumptions about disk use based on any experience you have gained from your production systems. Build a benchmark that looks like your production traffic, by all means, but don't extrapolate from 7.x to later versions for I/O information. There have been several huge strides in recent releases in reducing unecessary I/O, and 7.4 is susceptible to "checkpoint storms" that make even the most exotic storage hardware fail to perform well under some circumstances. Are your estimates of size, &c., based on a fresh load of the data? There are some lost-space issues in 7.4 that are solved in later releases, so you might find that some of your estimates of size are a little high. This matters for I/O, and might also affect your decision. > Also are there tools out there that monitor disk I/O and disk speed? Your OS should provide several. The basic ones are iostat and vmstat, but AIX has its own totally strange variants, and Solaris has some marvellous I/O tools. A