From: pinker <pinker@onet.eu>
To: pgsql-performance@postgresql.org
Subject: Checkpoints tuning
Date: Thu, 23 Oct 2014 06:24:00 -0700 (PDT)
Message-ID: <1414070640656-5824026.post@n5.nabble.com> (raw)
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
I have saved data from pg_stat_bgwriter view following Greg Smith's advice
from his book:
select now(),* from pg_stat_bgwriter;
and then aggregated the data with query from his book as well.
checkpoint segments was first 30 and next day I have increased it to 200,
and results has changed:
<http://postgresql.1045698.n5.nabble.com/file/n5824026/Auswahl_235.png;
now percent of checkpoints required because of number of segments is bigger
and backend writer share is also too high- I assume it's not what should
happen.
I'm not sure how to interpret correlation between allocation and written
data?
The bigger amount of data written per sec is a good sign?
--
View this message in context: http://postgresql.1045698.n5.nabble.com/Checkpoints-tuning-tp5824026.html
Sent from the PostgreSQL - performance mailing list archive at Nabble.com.
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: pinker@onet.eu
Subject: Re: Checkpoints tuning
In-Reply-To: <1414070640656-5824026.post@n5.nabble.com>
* 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