pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Aaron Birkland <birkie@gmail.com>
To: josh@agliodbs.com
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Why would writes to pgsql_tmp bottleneck at 1mb/s?
Date: Tue, 8 Mar 2005 20:13:29 -0500
Message-ID: <19ab0ccd05030817132e702cd4@mail.gmail.com> (raw)
In-Reply-To: <200503081644.32497.josh@agliodbs.com>
References: <200503081218.24093.josh@agliodbs.com>
	<200503081617.57190.josh@agliodbs.com>
	<200503081644.32497.josh@agliodbs.com>

> Maybe I'm not an idiot (really!)  even with almost 2GB of maintenance_mem, PG
> still writes to pgsql_tmp no faster than 2MB/s.    I think there may be an
> artificial bottleneck there.  Question is, PostgreSQL, OS or hardware?

I'm curious: what is your cpu usage while this is happening?  I've
noticed similar slow index creation behaviour, but I did not make any
connection to pgsql_temp (because it was not on a separate partition).
 I was indexing an oid field of a 700GB table and it took about four
days on a 1.2GHz UltraSparcIII (solaris 9, 8GB core).  I noticed that
the one CPU that was  pegged at near 100%, leading me to believe it
was CPU bound.  Odd thing is that the same operation on a 2GHz Pentium
IV box (Linux) on the same data took about a day.    Truss showed that
a great majority of that time was in userland.

    -Aaron



view thread (8+ messages)  latest in thread

Message-ID: <19ab0ccd05030817132e702cd4@mail.gmail.com>
Permalink:  ../19ab0ccd05030817132e702cd4@mail.gmail.com/
Also on:    postgresql.org/message-id/19ab0ccd05030817132e702cd4@mail.gmail.com

 · 

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: birkie@gmail.com, josh@agliodbs.com
  Subject: Re: Why would writes to pgsql_tmp bottleneck at 1mb/s?
  In-Reply-To: <19ab0ccd05030817132e702cd4@mail.gmail.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