From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Christopher Petrilli <petrilli(at)gmail(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Impact of checkpoint_segments under continual load conditions |
Date: | 2005-07-17 18:15:54 |
Message-ID: | 18942.1121624154@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Christopher Petrilli <petrilli(at)gmail(dot)com> writes:
> I have a unique scenerio. My DB is under "continual load", meaning
> that I am constantly using COPY to insert new data into the DB. There
> is no "quiet period" for the database, at least not for hours on end.
> Normally, checkpoint_segments can help absorb some of that, but my
> experience is that if I crank the number up, it simply delays the
> impact, and when it occurs, it takes a VERY long time (minutes) to
> clear.
If you are using 8.0, you can probably alleviate the problem by making
the bgwriter more aggressive. I don't have any immediate
recommendations for specific settings though.
A small checkpoint_segments setting is definitely bad news for
performance under heavy load.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Creager | 2005-07-18 03:34:16 | Huge performance problem between 7.4.1 and 8.0.3 - CS issue? |
Previous Message | Christopher Petrilli | 2005-07-17 17:08:34 | Impact of checkpoint_segments under continual load conditions |