Re: : PG9.0 - Checkpoint tuning and pg_stat_bgwriter

From: Venkat Balaji <venkat(dot)balaji(at)verse(dot)in>
To: Greg Smith <greg(at)2ndquadrant(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: : PG9.0 - Checkpoint tuning and pg_stat_bgwriter
Date: 2011-10-05 02:50:18
Message-ID: CAFrxt0gZSCofPJSystj4ct+w5Dee6sek_3LmHF4Y34cYARzwJQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

I was thinking to increase checkpoint_segments to around 16 or 20.

I think 50 is a bit higher.

Greg,

Sure. I would collect the info from pg_stat_bgwriter on regular intervals.

As we have too many transactions going on I am thinking to collect the info
every 6 or 8 hrs.

Thanks
VB

On Wed, Oct 5, 2011 at 4:02 AM, Greg Smith <greg(at)2ndquadrant(dot)com> wrote:

> On 10/04/2011 03:50 AM, Venkat Balaji wrote:
>
>> I had a look at the pg_stat_bgwriter as well.
>>
>
> Try saving it like this instead:
>
> select now(),* from pg_stat_bgwriter;
>
> And collect two data points, space a day or more apart. That gives a lot
> more information about the rate at which things are actually happening. The
> long-term totals are less interesting than that.
>
> Generally the first round of tuning work here is to increase
> checkpoint_segments until most checkpoints appear in checkpoints_timed
> rather than checkpoints_req. After that, increasing checkpoint_timeout
> might also be useful.
>
> --
> Greg Smith 2ndQuadrant US greg(at)2ndQuadrant(dot)com Baltimore, MD
> PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us
>
>
>
> --
> Sent via pgsql-performance mailing list (pgsql-performance(at)postgresql(dot)**
> org <pgsql-performance(at)postgresql(dot)org>)
> To make changes to your subscription:
> http://www.postgresql.org/**mailpref/pgsql-performance<http://www.postgresql.org/mailpref/pgsql-performance>
>

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Greg Smith 2011-10-05 05:32:09 Re: : PG9.0 - Checkpoint tuning and pg_stat_bgwriter
Previous Message Kevin Grittner 2011-10-04 23:33:23 Re: Query with order by and limit is very slow - wrong index used