From: Roger Ging <rging@musicreports.com>
To: pgsql-admin@postgresql.org
Subject: Vacuum wait time problem
Date: Fri, 13 Feb 2009 09:20:00 -0800
Message-ID: <4995ABC0.4090401@musicreports.com> (raw)
Hi,
I'm running vacuum full analyze verbose on a table with 20million rows
and 11 indexes. In top, I'm seeing [pdflush] and postgres: writer
process each using diferent cpu cores, with wait time well above 90% on
each of them. The vacuum has been running for several hours, and the
last thing to show on screen, over an hour ago, was :
DETAIL: 8577281 index row versions were removed.
736 index pages have been deleted, 736 are currently reusable.
CPU 7.57s/52.52u sec elapsed 381.70 sec.
That's the last index
The vacuum process itself is using less than 2% of a core.
The pg version is 8.3.1 running on Suse. Hardware is 2X dual core
Opterons, 16 GB RAM, 24 drives in RAID 50
It would seem to me that the system is extremely IO bound, but I don't
know how to find out what specifically is wrong here. Any advice
greatly appreciated.
--
Roger Ging
--
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: rging@musicreports.com
Subject: Re: Vacuum wait time problem
In-Reply-To: <4995ABC0.4090401@musicreports.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