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
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-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

Browse pgsql-hackers by date

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

Browse pgsql-patches by date

  From Date Subject
Next Message Greg Smith 2007-06-06 18:05:35 Re: Controlling Load Distributed Checkpoints
Previous Message Gregory Stark 2007-06-06 14:14:14 Re: Controlling Load Distributed Checkpoints