From: Steve Crawford <scrawford@pinpointresearch.com>
To: Craig James <craig_james@emolecules.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Who is causing all this i/o?
Date: Fri, 20 May 2011 16:08:14 -0700
Message-ID: <4DD6F45E.6000206@pinpointresearch.com> (raw)
In-Reply-To: <4DD6D9A6.1010101@emolecules.com>
References: <4DD6D9A6.1010101@emolecules.com>
On 05/20/2011 02:14 PM, Craig James wrote:
> Our development server (PG 8.4.4 on Ubuntu server) is constantly doing
> something, and I can't figure out what. The two production servers,
> which are essentially identical, don't show these symptoms. In a
> nutshell, it's showing 10K blocks per second of data going out, all
> the time, and essentially zero blocks per second of input.
...
There are people on this list better equipped than I to get into the
guts of diagnosis, but a quick Google shows you aren't the only person
to see high IO with disk activity. There are suggestions that a db with
lots of temp-table creation and nothing triggering a vacuum could be
related. Another thread suggested that bloated system tables could be to
blame. Others look at the stats collectors. Groping a bit in the dark, I
would try...
Checking PG logs for info - especially anything indicating that vacuum
isn't running or isn't being triggered.
Manual vacuum.
Vacuum full of system tables (pg_catalog - especially pg_class and
pg_attribute) - possibly followed by a reindex all followed by a manual
vacuum. Note: IIRC, that file is shared across databases so you will
need to clean each one.
Reset stats collector at startup.
Check system after each change and report back if anything improves or
degrades the situation.
Cheers,
Steve
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-admin@postgresql.org
Cc: scrawford@pinpointresearch.com, craig_james@emolecules.com
Subject: Re: Who is causing all this i/o?
In-Reply-To: <4DD6F45E.6000206@pinpointresearch.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