From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ralph Mason <ralph.mason@telogis.com>
Cc: 'Richard Huxton' <dev@archonet.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Ever Increasing IOWAIT
Date: Sun, 20 May 2007 17:55:50 -0400
Message-ID: <17450.1179698150@sss.pgh.pa.us> (raw)
In-Reply-To: <005b01c79b1f$20aeb340$620c19c0$@mason@telogis.com>
References: <011b01c798d5$141365a0$3c3a30e0$@mason@telogis.com>
<464D6DE1.6040001@archonet.com>
<005b01c79b1f$20aeb340$620c19c0$@mason@telogis.com>
"Ralph Mason" <ralph.mason@telogis.com> writes:
> Ralph Mason wrote:
>> We have a database running on a 4 processor machine. As time goes by
>> the IO gets worse and worse peeking at about 200% as the machine loads up.
>>
>> The weird thing is that if we restart postgres it's fine for hours but
>> over time it goes bad again.
Do you by any chance have stats collection enabled and
stats_reset_on_server_start set to true? If so, maybe this is explained
by growth in the size of the stats file over time. It'd be interesting
to keep an eye on the size of $PGDATA/global/pgstat.stat over a fast-to-
slow cycle.
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, ralph.mason@telogis.com, dev@archonet.com
Subject: Re: Ever Increasing IOWAIT
In-Reply-To: <17450.1179698150@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