From: Tom Lane <tgl@sss.pgh.pa.us>
To: Brad Nicholson <bnichols@ca.afilias.info>
Cc: pgsql-performance@postgresql.org
Subject: Re: Investigating IO Saturation
Date: Tue, 24 Jan 2006 12:07:38 -0500
Message-ID: <19963.1138122458@sss.pgh.pa.us> (raw)
In-Reply-To: <43D65736.9020905@ca.afilias.info>
References: <43D65736.9020905@ca.afilias.info>
Brad Nicholson <bnichols@ca.afilias.info> writes:
> I'm investigating a potential IO issue. We're running 7.4 on AIX 5.1.
> During periods of high activity (reads, writes, and vacuums), we are
> seeing iostat reporting 100% disk usage. I have a feeling that the
> iostat numbers are misleading. I can make iostat usage jump from less
> than 10% to greater than 95% by running a single vacuum against a
> moderate sized table (no noticeable change in the other activity).
That's not particularly surprising, and I see no reason to think that
iostat is lying to you.
More recent versions of PG include parameters that you can use to
"throttle" vacuum's I/O demand ... but unthrottled, it's definitely
an I/O hog.
The vmstat numbers suggest that vacuum is not completely killing you,
but you could probably get some improvement in foreground query
performance by throttling it back. There are other good reasons to
consider an update, anyway.
regards, tom lane
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: tgl@sss.pgh.pa.us, bnichols@ca.afilias.info
Subject: Re: Investigating IO Saturation
In-Reply-To: <19963.1138122458@sss.pgh.pa.us>
* 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