From: Joe Conway <mail@joeconway.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance <pgsql-performance@postgresql.org>
Subject: Re: rapid degradation after postmaster restart
Date: Sat, 13 Mar 2004 08:03:25 -0800
Message-ID: <405330CD.4050304@joeconway.com> (raw)
In-Reply-To: <18481.1079192379@sss.pgh.pa.us>
References: <4052661D.5060505@joeconway.com>
<18481.1079192379@sss.pgh.pa.us>
Tom Lane wrote:
> Just to be clear on this: you have to restart the postmaster to bring
> the time back down? Simply starting a fresh backend session doesn't do
> it?
Yes, a full postmaster restart is needed. It is a command line script
that does the insert, so each one is a new backend.
> Are you using particularly large values for shared_buffers or any of the
> other resource parameters?
I'll have to look at this again (I have to vpn in to the company lan
which kills all my current connections) -- the server and application
belong to another department at my employer.
IIRC, shared buffers was reasonable, maybe 128MB. One thing that is
worthy of note is that they are using pg_autovacuum and a very low
vacuum_mem setting (1024). But I also believe that max_fsm_relations and
max_fsm_pages have been bumped up from default (something like 10000 &
200000).
I'll post the non-default postgresql.conf settings shortly. The extended
tests discussed in the nearby post will take a bit more time to get.
Thanks,
Joe
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: mail@joeconway.com, tgl@sss.pgh.pa.us
Subject: Re: rapid degradation after postmaster restart
In-Reply-To: <405330CD.4050304@joeconway.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