pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim C. Nasby <jnasby@pervasive.com>
To: Marcin Giedz <marcin.giedz@eulerhermes.pl>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: Xeon vs Opteron - second revision - tests and questions
Date: Mon, 14 Nov 2005 11:50:51 -0600
Message-ID: <20051114175051.GE18570@pervasive.com> (raw)
In-Reply-To: <4374F071.9010808@eulerhermes.pl>
References: <200511091526.51685.marcin.giedz@eulerhermes.pl>
	<18347.1131563949@sss.pgh.pa.us>
	<4374E57F.5030201@eulerhermes.pl>
	<20815.1131736317@sss.pgh.pa.us>
	<4374F071.9010808@eulerhermes.pl>

On Fri, Nov 11, 2005 at 08:26:41PM +0100, Marcin Giedz wrote:
> Tom Lane napisa?(a):
> 
> >Marcin Giedz <marcin.giedz@eulerhermes.pl> writes:
> > 
> >
> >>However I still can see 'spikey' performance but  not as much as  before 
> >>changes.  What can I do  more to  eliminate or smooth these spikes?
> >>   
> >>
> >
> >The spikes are certainly caused by checkpoints.  You can fool with the
> >checkpoint timing via checkpoint_segments and checkpoint_timeout.
> > 
> >
> I didn't mention before  but I changed checkpoint_segments to 300 but no 
> checkpoint_time.  Disk space doesn't matter at all ... time to 
> recovery.... shouldn't be very long (I don't have much experiences with 
> this as I do online backup every day). Can anyone please tell me what 
> values of these two parametres are reasonable?

What Tom was refering to about 'time to recovery' is recovering from an
unexpected database shutdown by replaying the WAL. If you go 5 minutes
between syncing WAL to the mainline storage, then a worst-case recovery
will take ~5 minutes (well, it could probably take longer, but it should
be a linear relationship). The longer you make checkpoint interval, the
longer you'll have to wait for the database to come back.
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461



view thread (4+ messages)

Message-ID: <20051114175051.GE18570@pervasive.com>
Permalink:  ../20051114175051.GE18570@pervasive.com/
Also on:    postgresql.org/message-id/20051114175051.GE18570@pervasive.com

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: jnasby@pervasive.com, marcin.giedz@eulerhermes.pl, tgl@sss.pgh.pa.us
  Subject: Re: Xeon vs Opteron - second revision - tests and questions
  In-Reply-To: <20051114175051.GE18570@pervasive.com>
  References: <200511091526.51685.marcin.giedz@eulerhermes.pl> <18347.1131563949@sss.pgh.pa.us> <4374E57F.5030201@eulerhermes.pl> <20815.1131736317@sss.pgh.pa.us> <4374F071.9010808@eulerhermes.pl> <20051114175051.GE18570@pervasive.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