From: Jim C. Nasby <jim@nasby.net>
To: pgsql-performance@postgresql.org
Subject: Poor pg_dump performance
Date: Sun, 7 Sep 2003 00:23:24 -0500
Message-ID: <20030907052324.GC37152@nasby.net> (raw)
First, sorry if this has been answered before; the list search seems to
be down...
This is on a quad Xeon-PII 450 machine running FBSD 4.8.
84386 pgsql 64 0 104M 99M RUN 1 78:20 61.87% 61.87% postgres
84385 decibel 64 0 3748K 2268K CPU1 3 49:49 37.79% 37.79% pg_dump
(note that the CPU percents are per-cpu, so 100% would be 100% of one
CPU)
According to vmstat, there's very little disk I/O, so that's not a
bottleneck. The command I used was:
pg_dump -vFc -f pgsql-20030906.cdb stats
It should be compressing, but if that was the bottleneck, shouldn't the
pg_dump process be at 100% CPU? It does seem a bit coincidental that the
two procs seem to be taking 100% of one CPU (top shows them running on
different CPUs though).
This is version 7.3.4.
--
Jim C. Nasby, Database Consultant jim@nasby.net
Member: Triangle Fraternity, Sports Car Club of America
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?"
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: jim@nasby.net
Subject: Re: Poor pg_dump performance
In-Reply-To: <20030907052324.GC37152@nasby.net>
References: <20030907052324.GC37152@nasby.net>
* 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