From: | Mark Kirkwood <markir(at)paradise(dot)net(dot)nz> |
---|---|
To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Raid 10 chunksize |
Date: | 2009-03-25 03:20:52 |
Message-ID: | 49C9A314.6050302@paradise.net.nz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Scott Marlowe wrote:
> 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.
>
>
Yeah, I was wondering if we are maxing out the bandwidth...
>> 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?
>
>
Yes - or I am hoping to anyway (part of posting here was to collect some
outside validation for the idea). Thanks for your input!
Cheers
Mark
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2009-03-25 03:29:17 | Re: Raid 10 chunksize |
Previous Message | marcin mank | 2009-03-25 03:04:08 | Re: Help Me Understand Why I'm Getting a Bad Query Plan |