"John Jensen" <[EMAIL PROTECTED]> writes:
> The job is clearly cpu bound in the postmaster process.
Which part of the dump process is CPU bound --- dumping schema, or data?
(Try enabling log_statement for the pg_dump run and correlating the
appearance of queries in the postmaster log with the CPU
John Jensen wrote:
Hi Greg & others.
I run this on a 4 cpu smp box (Dell PE6650+EMC AX100) so I already
offload pg_dump, gzip and split to other cpu's. Top confirms this:
postmaster = 95% cpu ie. it uses one cpu completely. Unless I can get
postmaster to do less work (that's what I'm looking for) o
tem snapshot, then release the locks.
I'm sure Tom, Josh or someone more in the know would have imput for
this option.
Greg
-Original Message-
From: John Jensen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 07, 2004 6:48 AM
To: [EMAIL PROTECTED]
Subject: [ADMIN] Backup is too s
EMAIL PROTECTED]
Subject: [ADMIN] Backup is too slow
Hi all,
I'm a bit unhappy with the time it takes to do backup of my PG7.4.6
base.
I have 13GB under the pg/data dir and it takes 30 minutes to do the
backup.
Using top and iostat I've figured out that the backup job is cpu bound
in the po
Hi all,
I'm a bit unhappy with the time it takes to do backup of my PG7.4.6
base.
I have 13GB under the pg/data dir and it takes 30 minutes to do the
backup.
Using top and iostat I've figured out that the backup job is cpu bound
in the postmaster process. It eats up 95% cpu while the disk is at 10
