Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 887E5B5DBC4 for ; Wed, 17 Aug 2011 16:22:31 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 70466-09 for ; Wed, 17 Aug 2011 19:22:25 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by mail.postgresql.org (Postfix) with ESMTP id 5A51AB5D803 for ; Wed, 17 Aug 2011 16:22:25 -0300 (ADT) Received: from [192.168.1.108] (unknown [173.165.13.38]) by smtp.mxes.net (Postfix) with ESMTPA id 079D422E247; Wed, 17 Aug 2011 15:22:24 -0400 (EDT) Subject: Re: Tuning Tips for a new Server Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii From: Ogden In-Reply-To: Date: Wed, 17 Aug 2011 14:22:24 -0500 Cc: Tomas Vondra , pgsql-performance@postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <959BD2FA-0312-458B-BD5F-ED358D2C47ED@darkstatic.com> <01b1e09ae6df37cd32543df0dee95bfa.squirrel@sq.gransy.com> To: Scott Marlowe X-Mailer: Apple Mail (2.1082) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201108/201 X-Sequence-Number: 44648 On Aug 17, 2011, at 2:14 PM, Scott Marlowe wrote: > On Wed, Aug 17, 2011 at 12:56 PM, Tomas Vondra wrote: >>=20 >> I think you've mentioned the database is on 6 drives, while the other >> volume is on 2 drives, right? That makes the OS drive about 3x slower >> (just a rough estimate). But if the database drive is used heavily, = it >> might help to move the xlog directory to the OS disk. See how is the = db >> volume utilized and if it's fully utilized, try to move the xlog >> directory. >>=20 >> The only way to find out is to actualy try it with your workload. >=20 > This is a very important point. I've found on most machines with > hardware caching RAID and 8 or fewer 15k SCSI drives it's just as > fast to put it all on one big RAID-10 and if necessary partition it to > put the pg_xlog on its own file system. After that depending on the > workload you might need a LOT of drives in the pg_xlog dir or just a > pair. Under normal ops many dbs will use only a tiny % of a > dedicated pg_xlog. Then something like a site indexer starts to run, > and writing heavily to the db, and the usage shoots to 100% and it's > the bottleneck. I suppose this is my confusion. Or rather I am curious about this. On my = current production database the pg_xlog directory is 8Gb (our total = database is 200Gb). Does this warrant a totally separate setup (and = hardware) than PGDATA?=