Re: rapid degradation after postmaster restart

From: "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>, pgsql-performance <pgsql-performance(at)postgresql(dot)org>, Josh Berkus <josh(at)agliodbs(dot)com>
Subject: Re: rapid degradation after postmaster restart
Date: 2004-03-17 05:12:20
Message-ID: 4057DE34.1080001@zeut.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-performance

On Tue, 2004-03-16 at 23:49, Joe Conway wrote:
> 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.

If memory serves, the problem is that you actually sleep 10ms even when
you set it to 1. One of the thing changed in Jan's later patch was the
ability to specify how many pages to work on before sleeping, rather
than how long to sleep inbetween every 1 page. You might be able to do
a quick hack and have it do 10 pages or so before sleeping.

Matthew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-03-17 05:17:40 Re: rapid degradation after postmaster restart
Previous Message Joe Conway 2004-03-17 04:49:01 Re: rapid degradation after postmaster restart

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2004-03-17 05:17:40 Re: rapid degradation after postmaster restart
Previous Message Joe Conway 2004-03-17 04:49:01 Re: rapid degradation after postmaster restart