From: Tom Lane <tgl@sss.pgh.pa.us>
To: Anjan Dave <adave@vantage.com>
Cc: Rod Taylor <pg@rbt.ca>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: can't handle large number of INSERT/UPDATEs
Date: Tue, 26 Oct 2004 17:53:14 -0400
Message-ID: <13823.1098827594@sss.pgh.pa.us> (raw)
In-Reply-To: <4BAFBB6B9CC46F41B2AD7D9F4BBAF7850985DD@vt-pe2550-001.vantage.vantage.com>
References: <4BAFBB6B9CC46F41B2AD7D9F4BBAF7850985DD@vt-pe2550-001.vantage.vantage.com>
"Anjan Dave" <adave@vantage.com> writes:
> None of the locks are in state false actually.
In that case you don't have a locking problem.
> I don't have iostat on that machine, but vmstat shows a lot of writes to
> the drives, and the runnable processes are more than 1:
I get the impression that you are just saturating the write bandwidth of
your disk :-(
It's fairly likely that this happens during checkpoints. Look to see if
the postmaster has a child that shows itself as a checkpointer in "ps"
when the saturation is occurring. You might be able to improve matters
by altering the checkpoint frequency parameters (though beware that
either too small or too large will likely make matters even worse).
regards, tom lane
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: tgl@sss.pgh.pa.us, adave@vantage.com, pg@rbt.ca
Subject: Re: can't handle large number of INSERT/UPDATEs
In-Reply-To: <13823.1098827594@sss.pgh.pa.us>
* 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