pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim C. Nasby <decibel@decibel.org>
To: Mischa Sandberg <mischa.sandberg@telus.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: Slow copy with little CPU/disk usage
Date: Wed, 20 Apr 2005 17:22:27 -0500
Message-ID: <20050420222227.GW58835@decibel.org> (raw)
In-Reply-To: <1113971840.4265dc810374c@webmail.telus.net>
References: <20050420020033.GZ58835@decibel.org>
	<19670.1113966354@sss.pgh.pa.us>
	<1113971840.4265dc810374c@webmail.telus.net>

No, this is a single process. And there's known issues with context
storms on Xeons, so that might be what you're seeing.

On Tue, Apr 19, 2005 at 09:37:21PM -0700, Mischa Sandberg wrote:
> Quoting Tom Lane <tgl@sss.pgh.pa.us>: 
>  
> > "Jim C. Nasby" <decibel@decibel.org> writes: 
> > > A friend of mine has an application where he's copying in 4000 rows at a 
> > > time into a table that has about 4M rows. Each row is 40-50 bytes. This 
> > > is taking 25 seconds on a dual PIII-1GHz with 1G of RAM and a 2 disk 
> > > SATA mirror, running FBSD 4.10-stable. There's one index on the table. 
> >  
> > If there's no hidden costs such as foreign key checks, that does seem 
> > pretty dang slow. 
> >  
> > > What's really odd is that neither the CPU or the disk are being 
> > > hammered. The box appears to be pretty idle; the postgresql proces is 
> > > using 4-5% CPU. 
> --  
> This sounds EXACTLY like my problem, if you make the box to a Xeon 2.4GHz, 2GB 
> RAM ... with two SCSI drives (xlog and base); loading 10K rows of about 200 
> bytes each; takes about 20 secs at the best, and much longer at the worst. By 
> any chance does your friend have several client machines/processes trying to 
> mass-load rows at the same time? Or at least some other processes updating 
> that table in a bulkish way? What I get is low diskio, low cpu, even low 
> context-switches ... and I'm betting he should take a look at pg_locks. For my 
> own problem, I gather that an exclusive lock is necessary while updating 
> indexes and heap, and the multiple processes doing the update can make that 
> pathological. 
>  
> Anyway, have your friend check pg_locks. 
>  
>  
> "Dreams come true, not free." -- S.Sondheim, ITW 
> 

-- 
Jim C. Nasby, Database Consultant               decibel@decibel.org 
Give your computer some brain candy! www.distributed.net Team #1828

Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"



view thread (6+ messages)  latest in thread

Message-ID: <20050420222227.GW58835@decibel.org>
Permalink:  ../20050420222227.GW58835@decibel.org/
Also on:    postgresql.org/message-id/20050420222227.GW58835@decibel.org

 · 

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: decibel@decibel.org, mischa.sandberg@telus.net, tgl@sss.pgh.pa.us
  Subject: Re: Slow copy with little CPU/disk usage
  In-Reply-To: <20050420222227.GW58835@decibel.org>

* 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