X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id DE4F63A638F for ; Sat, 11 Dec 2004 07:56:43 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 58439-07 for ; Sat, 11 Dec 2004 07:56:37 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 655A93A6408 for ; Sat, 11 Dec 2004 07:55:24 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.13.1/8.13.1) with ESMTP id iBB7tLJG059214 for ; Sat, 11 Dec 2004 07:55:21 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.13.1/8.13.1/Submit) id iBB7kgjD057350 for pgsql-admin@postgresql.org; Sat, 11 Dec 2004 07:46:42 GMT (envelope-from news) From: William Yu X-Newsgroups: pgsql.admin Subject: Re: Backup is too slow Date: Fri, 10 Dec 2004 23:45:50 -0800 Organization: Hub.Org Networking Services Lines: 22 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@news.hub.org User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en In-Reply-To: To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Archive-Number: 200412/82 X-Sequence-Number: 15668 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.