From: Ogden <lists@darkstatic.com>
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: Tomas Vondra <tv@fuzzy.cz>
Cc: pgsql-performance@postgresql.org
Subject: Re: Tuning Tips for a new Server
Date: Wed, 17 Aug 2011 14:22:24 -0500
Message-ID: <D256F08F-38C0-45B9-A742-753629386DB5@darkstatic.com> (raw)
In-Reply-To: <CAOR=d=0NAmTbYE1epENHiP0UjbivpPvzwC2z951YQBuja86z2Q@mail.gmail.com>
References: <959BD2FA-0312-458B-BD5F-ED358D2C47ED@darkstatic.com>
<f4e06a7cad34ee9217a3e57fd4eb0e67.squirrel@sq.gransy.com>
<D89151D3-D2E5-47E3-8B90-4A573DAB5FFA@darkstatic.com>
<01b1e09ae6df37cd32543df0dee95bfa.squirrel@sq.gransy.com>
<CAOR=d=0NAmTbYE1epENHiP0UjbivpPvzwC2z951YQBuja86z2Q@mail.gmail.com>
On Aug 17, 2011, at 2:14 PM, Scott Marlowe wrote:
> On Wed, Aug 17, 2011 at 12:56 PM, Tomas Vondra <tv@fuzzy.cz> wrote:
>>
>> 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.
>>
>> The only way to find out is to actualy try it with your workload.
>
> 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?
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: lists@darkstatic.com, scott.marlowe@gmail.com, tv@fuzzy.cz
Subject: Re: Tuning Tips for a new Server
In-Reply-To: <D256F08F-38C0-45B9-A742-753629386DB5@darkstatic.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