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

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?

Regards,
Marcin


>Usually people put them as far apart as they can stand (the constraint
>on this is mainly how long you'd like to wait for recovery after a
>system crash, and how much disk space you can spare for WAL logs).
>Increasing the bg_writer parameters can be expected to dampen the spikes
>but not eliminate them completely.
>
>			regards, tom lane
>
>  
>




view thread (4+ messages)  latest in thread

Message-ID: <4374F071.9010808@eulerhermes.pl>
Permalink:  ../4374F071.9010808@eulerhermes.pl/
Also on:    postgresql.org/message-id/4374F071.9010808@eulerhermes.pl

 · 

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: marcin.giedz@eulerhermes.pl, tgl@sss.pgh.pa.us, jnasby@pervasive.com
  Subject: Re: Xeon vs Opteron - second revision - tests and questions
  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>

* 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