From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Mark Kirkwood <markir(at)paradise(dot)net(dot)nz> |
Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Raid 10 chunksize |
Date: | 2009-03-25 02:11:07 |
Message-ID: | dcc563d10903241911p29f604vfd9025a106d0eac3@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Tue, Mar 24, 2009 at 7:09 PM, Mark Kirkwood <markir(at)paradise(dot)net(dot)nz> wrote:
> I'm trying to pin down some performance issues with a machine where I work,
> we are seeing (read only) query response times blow out by an order of
> magnitude or more at busy times. Initially we blamed autovacuum, but after a
> tweak of the cost_delay it is *not* the problem. Then I looked at
> checkpoints... and altho there was some correlation with them and the query
> response - I'm thinking that the raid chunksize may well be the issue.
Sounds to me like you're mostly just running out of bandwidth on your
RAID array. Whether or not you can tune it to run faster is the real
issue. This problem becomes worse as you add clients and the RAID
array starts to thrash. Thrashing is likely to be worse with a small
chunk size, so that's definitely worth a look at fixing.
> Fortunately there is an identical DR box, so I could do a little testing.
Can you try changing the chunksize on the test box you're testing on
to see if that helps?
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2009-03-25 02:30:10 | Re: Help Me Understand Why I'm Getting a Bad Query Plan |
Previous Message | David Rees | 2009-03-25 02:04:42 | Re: Raid 10 chunksize |