pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jeffrey Baker <jwbaker@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: 3-days-long vacuum of 20GB table
Date: Fri, 18 Apr 2008 15:09:08 -0400
Message-ID: <6256.1208545748@sss.pgh.pa.us> (raw)
In-Reply-To: <fd145f7d0804181054g6642d197n458f0b62edd79f6a@mail.gmail.com>
References: <fd145f7d0804180935w7d0052degf79a9660b043c084@mail.gmail.com>
	<3630.1208538238@sss.pgh.pa.us>
	<fd145f7d0804181032w5dd56caj608866297120984a@mail.gmail.com>
	<fd145f7d0804181034j50ffb420s4b4144636d886087@mail.gmail.com>
	<fd145f7d0804181054g6642d197n458f0b62edd79f6a@mail.gmail.com>

"Jeffrey Baker" <jwbaker@gmail.com> writes:
> I increased it to 1GB, restarted the vacuum, and system performance
> seems the same.  The root of the problem, that an entire CPU is in the
> iowait state and the storage device is doing random i/o, is unchanged:

Yeah, but you just reduced the number of index scans that will be needed
by a factor of 1GB/16MB.  Hang in there ...

			regards, tom lane

view thread (8+ messages)  latest in thread

Message-ID: <6256.1208545748@sss.pgh.pa.us>
Permalink:  ../6256.1208545748@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/6256.1208545748@sss.pgh.pa.us

copy link · copy postgr.es

reply

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, jwbaker@gmail.com
  Subject: Re: 3-days-long vacuum of 20GB table
  In-Reply-To: <6256.1208545748@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