pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Joe Conway <mail@joeconway.com>
Cc: Matthew T. O'Connor <matthew@zeut.net>
Cc: pgsql-performance <pgsql-performance@postgresql.org>
Cc: Josh Berkus <josh@agliodbs.com>
Subject: Re: rapid degradation after postmaster restart
Date: Wed, 17 Mar 2004 00:17:40 -0500
Message-ID: <21011.1079500660@sss.pgh.pa.us> (raw)
In-Reply-To: <4057D8BD.4080902@joeconway.com>
References: <4052661D.5060505@joeconway.com>
	<14884.1079150555@sss.pgh.pa.us>
	<4055F343.6070600@joeconway.com>
	<405614CA.5030101@zeut.net>
	<405689A4.4080406@joeconway.com>
	<16735.1079414723@sss.pgh.pa.us>
	<4057D8BD.4080902@joeconway.com>

Joe Conway <mail@joeconway.com> writes:
> I have tested Tom's original patch now. The good news -- it works great 
> in terms of reducing the load imposed by vacuum -- almost to the level 
> of being unnoticeable. The bad news -- in a simulation test which loads 
> an hour's worth of data, even with delay set to 1 ms, vacuum of the 
> large table exceeds two hours (vs 12-14 minutes with delay = 0). Since 
> that hourly load is expected 7 x 24, this obviously isn't going to work.

Turns the dial down a bit too far then ...

> The problem with Jan's more complex version of the patch (at least the 
> one I found - perhaps not the right one) is it includes a bunch of other 
> experimental stuff that I'd not want to mess with at the moment. Would 
> changing the input units (for the original patch) from milli-secs to 
> micro-secs be a bad idea?

Unlikely to be helpful; on most kernels the minimum sleep delay is 1 or
10 msec, so asking for a few microsec is the same as asking for some
millisec.  I think what you need is a knob of the form "sleep N msec
after each M pages of I/O".  I'm almost certain that Jan posted such a
patch somewhere between my original and the version you refer to above.

			regards, tom lane



view thread (26+ messages)  latest in thread

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

 · 

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, mail@joeconway.com, matthew@zeut.net, josh@agliodbs.com
  Subject: Re: rapid degradation after postmaster restart
  In-Reply-To: <21011.1079500660@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