Skip site navigation (1) Skip section navigation (2)

Re: Controlling Load Distributed Checkpoints

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, Greg Smith <gsmith(at)gregsmith(dot)com>
Subject: Re: Controlling Load Distributed Checkpoints
Date: 2007-06-06 15:03:25
Message-ID: 21062.1181142205@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Heikki Linnakangas <heikki(at)enterprisedb(dot)com> writes:
> GUC summary and suggested default values
> ----------------------------------------
> checkpoint_write_percent = 50 		# % of checkpoint interval to spread out 
> writes
> checkpoint_write_min_rate = 1000	# minimum I/O rate to write dirty 
> buffers at checkpoint (KB/s)
> checkpoint_nap_duration = 2 		# delay between write and sync phase, in 
> seconds
> checkpoint_fsync_period = 30		# duration of the sync phase, in seconds
> checkpoint_fsync_delay = 500		# max. delay between fsyncs

> I don't like adding that many GUC variables, but I don't really see a 
> way to tune them automatically.

If we don't know how to tune them, how will the users know?  Having to
add that many variables to control one feature says to me that we don't
understand the feature.

Perhaps what we need is to think about how it can auto-tune itself.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2007-06-06 15:23:00
Subject: Re: Implicit casts with generic arrays
Previous:From: Bruce MomjianDate: 2007-06-06 14:41:23
Subject: Re: TOAST usage setting

pgsql-patches by date

Next:From: Greg SmithDate: 2007-06-06 18:05:35
Subject: Re: Controlling Load Distributed Checkpoints
Previous:From: Gregory StarkDate: 2007-06-06 14:14:14
Subject: Re: Controlling Load Distributed Checkpoints

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group