From: Vinubalaji Gopal <vgopal@abaca.com>
To: Joshua D. Drake <jd@commandprompt.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: vacuum in Postgresql 8.0.x slowing down the database
Date: Thu, 27 Mar 2008 23:28:33 -0800
Message-ID: <20080327232833.4d84b68b@vinu-ubuntu.abaca> (raw)
In-Reply-To: <20080326130213.3797bfe1@jd-laptop>
References: <20080326124956.49e1c13d@vinu-ubuntu.abaca>
<20080326130213.3797bfe1@jd-laptop>
On Wed, 26 Mar 2008 13:02:13 -0700
"Joshua D. Drake" <jd@commandprompt.com> wrote:
> The slowness is likely attributed to Vacuum's use of I/O. When vacuum
> is running what does iostat -k 10 say?
Seems to be higher than normal - here is the output with vacuum run
without the other queries and the default vacuum taking ~1 hr:
avg-cpu: %user %nice %system %iowait %steal %idle
13.30 0.00 4.50 25.91 0.00 56.29
Device: tps kB_read/s kB_wrtn/s kB_read kB_wrtn
md2 3356.94 2005.59 12945.45 20076 129584
avg-cpu: %user %nice %system %iowait %steal %idle
16.20 0.00 6.32 24.89 0.00 52.59
Device: tps kB_read/s kB_wrtn/s kB_read kB_wrtn
md2 461.70 667.20 1512.00 6672 15120
I don't know if the output helps much since the vacuum took some time
and I lost more than half of my iostat -k screen output. (I scrolled up
- but got only some of the data)
If vacuum does affect the io what are the ways to reduce the io during
vacuum (the delay and cost parameter did not help that much - should I
consider reducing the cost even further)? Should I consider
partitioning the table?
Thank you.
--
Vinu
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: vgopal@abaca.com, jd@commandprompt.com
Subject: Re: vacuum in Postgresql 8.0.x slowing down the database
In-Reply-To: <20080327232833.4d84b68b@vinu-ubuntu.abaca>
* 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