From: KONDO Mitsumasa <kondo.mitsumasa@lab.ntt.co.jp>
To: Tasos Petalas <tasos.petalas@upstreamsystems.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: PG performance issues related to storage I/O waits
Date: Thu, 01 Aug 2013 11:02:06 +0900
Message-ID: <51F9C19E.7010105@lab.ntt.co.jp> (raw)
In-Reply-To: <21cb334b6ca0c09c4faa60bdd46179eb@mail.gmail.com>
References: <21cb334b6ca0c09c4faa60bdd46179eb@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
Hi Tasos,
(2013/07/31 20:58), Tasos Petalas wrote:
> We have set synchronous_commit to off but since almost all of application queries
> are using prepared statements we don't get any real benefit.
> Also please advise on any postgres.conf modification that could significantly
> affect storage load (WAL-checkpoint configuration etc.)
Please send us to your postgresql.conf and detail of your server (memory ,raid
cache size and OS version).
I think your server's memory is big. You should set small dirty_background_ratio
or dirty_background_byte. If your server's memory is big, PostgreSQL's checkpoint
executes stupid disk-write.
By the way, I make new checkpoint scheduler and method now. If you could send
more detail information which is like response time or load average, you will
help me to make better my patch.
Best regards,
--
Mitsumasa KONDO
NTT Open Source Software Center
--
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: kondo.mitsumasa@lab.ntt.co.jp, tasos.petalas@upstreamsystems.com
Subject: Re: PG performance issues related to storage I/O waits
In-Reply-To: <51F9C19E.7010105@lab.ntt.co.jp>
* 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