From: Greg Smith <greg@2ndquadrant.com>
To: Andy Colson <andy@squeakycode.net>
Cc: Craig Ringer <craig@postnewspapers.com.au>
Cc: pgsql-performance@postgresql.org
Subject: Re: a heavy duty operation on an "unused" table kills my server
Date: Thu, 14 Jan 2010 13:07:44 -0500
Message-ID: <4B4F5D70.4020103@2ndquadrant.com> (raw)
In-Reply-To: <4B4F2F00.7070401@squeakycode.net>
References: <e24c1d9d1001122059ic5d4721o98ccf85033b1fead@mail.gmail.com>
<4B4D5698.8040808@emolecules.com>
<e24c1d9d1001122147l1c0e2111kce25dc2c7f393087@mail.gmail.com>
<4B4D61DA.7080008@postnewspapers.com.au>
<e24c1d9d1001122303g1d4eea48h18bd73467d1fa8ec@mail.gmail.com>
<603c8f071001130823l69804fe3m5c6fbb081c55c265@mail.gmail.com>
<4B4EAD76.9030305@postnewspapers.com.au>
<4B4F2F00.7070401@squeakycode.net>
Andy Colson wrote:
> On 1/13/2010 11:36 PM, Craig Ringer wrote:
>> Yes. My 3ware 8500-8 on a Debian Sarge box was so awful that launching a
>> terminal would go from a 1/4 second operation to a 5 minute operation
>> under heavy write load by one writer. I landed up having to modify the
>> driver to partially mitigate the issue, but a single user on the
>> terminal server performing any sort of heavy writing would still
>> absolutely nuke performance.
>
> On a side note, on linux, would using the deadline scheduler resolve
> that?
I've never seen the deadline scheduler resolve anything. If you're out
of I/O capacity and that's blocking other work, performance is dominated
by the policies of the underlying controller/device caches. Think about
it a minute: disks nowadays can easily have 32MB of buffer in them,
right? And random read/write operations are lucky to clear 2MB/s on
cheap drivers. So once the drive is filled with requests, you can
easily sit there for ten seconds before the scheduler even has any input
on resolving the situation. That's even more true if you've got a
larger controller cache in the mix.
--
Greg Smith 2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
greg@2ndQuadrant.com www.2ndQuadrant.com
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: greg@2ndquadrant.com, andy@squeakycode.net, craig@postnewspapers.com.au
Subject: Re: a heavy duty operation on an "unused" table kills my server
In-Reply-To: <4B4F5D70.4020103@2ndquadrant.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