pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Andreas Kostyrka <andreas@kostyrka.org>
To: Ben <bench@silentmedia.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: big transaction slows down over time - but disk
Date: Wed, 01 Nov 2006 10:21:01 +0100
Message-ID: <1162372861.18283.34.camel@andi-lap> (raw)
In-Reply-To: <Pine.LNX.4.64.0610312141430.5452@GRD.cube42.tai.silentmedia.com>
References: <Pine.LNX.4.64.0610312141430.5452@GRD.cube42.tai.silentmedia.com>

Am Dienstag, den 31.10.2006, 21:58 -0800 schrieb Ben:
> I've got a long-running, update-heavy transaction that increasingly slows 
> down the longer it runs. I would expect that behavior, if there was some 
> temp file creation going on. But monitoring vmstat over the life of the 
> transaction shows virtually zero disk activity. Instead, the system has 
> its CPU pegged the whole time.
> 
> So.... why the slowdown? Is it a MVCC thing? A side effect of calling 
> stored proceedures a couple hundred thousand times in a single 

Memory usage? Have you tried to checkpoint your transaction from time to
time?

Andreas

> transaction? Or am I just doing something wrong?
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings

Attachments:

  signature.asc (application/pgp-signature, 188B) download

view thread (8+ messages)  latest in thread

Message-ID: <1162372861.18283.34.camel@andi-lap>
Permalink:  ../1162372861.18283.34.camel@andi-lap/
Also on:    postgresql.org/message-id/1162372861.18283.34.camel@andi-lap

 · 

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: andreas@kostyrka.org, bench@silentmedia.com
  Subject: Re: big transaction slows down over time - but disk
  In-Reply-To: <1162372861.18283.34.camel@andi-lap>

* 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