Re: rapid degradation after postmaster restart

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: pgsql-performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: rapid degradation after postmaster restart
Date: 2004-03-13 04:02:35
Message-ID: 14884.1079150555@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-performance

Joe Conway <mail(at)joeconway(dot)com> writes:
> The problem is this: the application runs an insert, that fires off a
> trigger, that cascades into a fairly complex series of functions, that
> do a bunch of calculations, inserts, updates, and deletes. Immediately
> after a postmaster restart, the first insert or two take about 1.5
> minutes (undoubtedly this could be improved, but it isn't the main
> issue). However by the second or third insert, the time increases to 7 -
> 9 minutes. Restarting the postmaster causes the cycle to repeat, i.e.
> the first one or two inserts are back to the 1.5 minute range.

I realize this question might take some patience to answer, but what
does the performance curve look like beyond three trials? Does it level
off or continue to get worse? If it doesn't level off, does the
degradation seem linear in the number of trials, or worse than linear?

I have no ideas in mind, just trying to gather data ...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Lamar Owen 2004-03-13 14:36:27 Re: Log rotation
Previous Message Jeroen T. Vermeulen 2004-03-13 03:33:59 Re: [HACKERS] The Name Game: postgresql.net vs.

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2004-03-13 15:39:39 Re: rapid degradation after postmaster restart
Previous Message Marty Scholes 2004-03-13 02:51:06 Re: rapid degradation after postmaster restart