From: William Yu <wyu@talisys.com>
To: pgsql-admin@postgresql.org
Subject: Re: Backup is too slow
Date: Fri, 10 Dec 2004 23:45:50 -0800
Message-ID: <cpe8l2$1nvt$1@news.hub.org> (raw)
In-Reply-To: <s1b5ccce.070@fs3.ft.fo>
References: <s1b5ccce.070@fs3.ft.fo>
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) or run multiple
> threads (not likely) that's about the best I can get.
>
> The job is clearly cpu bound in the postmaster process.
Hmmm, when I upgraded my Opteron box to 64-bit linux, my dump->gzip ran
twice as fast which told me the gzip was a bit part of the CPU usage.
Dunno what else you can do to make it run faster. My backups -- even on
64-bit -- still take 20 minutes on a 30GB DB.
>
> I'm a bit reluctant to go into the snapshot option You outline. It
> looks a bit tricky but if no other options are on hand then I'll have to
> bite the bullet.
Snapshot is much easier if you use LVM. No need to do any postgres
trickery. Just freeze the volume at the kernel level.
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-admin@postgresql.org
Cc: wyu@talisys.com
Subject: Re: Backup is too slow
In-Reply-To: <cpe8l2$1nvt$1@news.hub.org>
References: <s1b5ccce.070@fs3.ft.fo> <cpe8l2$1nvt$1@news.hub.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