Re: Impact of checkpoint_segments under continual load conditions

From: Christopher Petrilli <petrilli(at)gmail(dot)com>
To: PFC <lists(at)boutiquenumerique(dot)com>, Vivek Khera <vivek(at)khera(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Impact of checkpoint_segments under continual load conditions
Date: 2005-07-19 15:44:00
Message-ID: 59d991c4050719084460b376f1@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On 7/19/05, PFC <lists(at)boutiquenumerique(dot)com> wrote:
>
> What happens if, say at iteration 6000 (a bit after the mess starts), you
> pause it for a few minutes and resume. Will it restart with a plateau like
> at the beginning of the test ? or not ?

Not sure... my benchmark is designed to represent what the database
will do under "typical" circumstances, and unfortunately these are
typical for the application. However, I can see about adding some
delays, though multiple minutes would be absurd in the application.
Perhaps a 5-10 second day? Would that still be interesting?

> What if, during this pause, you disconnect and reconnect, or restart the
> postmaster, or vacuum, or analyze ?

Well, I don't have the numbers any more, but restarting the postmaster
has no effect, other than the first few hundreds COPYs are worse than
anything (3-4x slower), but then it goes back to following the trend
line. The data in the chart for v8.0.3 includes running pg_autovacuum
(5 minutes).

Chris
--
| Christopher Petrilli
| petrilli(at)gmail(dot)com

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2005-07-19 15:57:27 Re: Impact of checkpoint_segments under continual load conditions
Previous Message PFC 2005-07-19 15:33:21 Re: Impact of checkpoint_segments under continual load conditions