pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Eric Comeau <ecomeau@signiant.com>
Cc: pgsql-performance@postgresql.org, mladen.gogala@vmsinfo.com, Kathryn Smith <Kathryn.Smith@signiant.com>
Subject: Re: Help with duration of statement: EXECUTE <unnamed> [PREPARE: COMMIT]
Date: Tue, 19 Oct 2010 10:25:34 -0400
Message-ID: <9954.1287498334@sss.pgh.pa.us> (raw)
In-Reply-To: <4CBD7FCD.3070302@signiant.com>
References: <i9c60b$ifv$1@news.hub.org>
	<18890.1287411233@sss.pgh.pa.us>
	<4CBC58CD.9010906@vmsinfo.com>
	<19782.1287414135@sss.pgh.pa.us>
	<4CBD7FCD.3070302@signiant.com>

Eric Comeau <ecomeau@signiant.com> writes:
> Okay - I'm starting to see other stmts other than just commits taking 
> longer than 5 secs sometimes as well now - stress test has been running 
> for 3 days now...some commits 17 and 15 secs ouch...

If it's not just commits then some of the stranger theories go away.
I think you're almost certainly looking at overstressed disk.

It'd be worth your while to turn on checkpoint logging and see if
the slow operations occur during checkpoints.  If so, you might be
able to ameliorate things by tweaking the checkpoint parameters
to spread out checkpoint I/O load some more.  But the bottom line
here is that you haven't got much headroom between your application's
needs and the max throughput available from your disk.  Better disk
hardware will be the only real cure.

			regards, tom lane



view thread (6+ messages)

Message-ID: <9954.1287498334@sss.pgh.pa.us>
Permalink:  ../9954.1287498334@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/9954.1287498334@sss.pgh.pa.us

 · 

reply

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, ecomeau@signiant.com, Kathryn.Smith@signiant.com
  Subject: Re: Help with duration of statement: EXECUTE <unnamed> [PREPARE: COMMIT]
  In-Reply-To: <9954.1287498334@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