pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: ktm@rice.edu <ktm@rice.edu>
To: Evgeny Shishkin <itparanoia@gmail.com>
Cc: Jeison Bedoya <jeisonb@audifarma.com.co>
Cc: pgsql-performance@postgresql.org
Subject: Re: performance database for backup/restore
Date: Tue, 21 May 2013 10:46:13 -0500
Message-ID: <20130521154613.GE12507@aart.rice.edu> (raw)
In-Reply-To: <39946120-F3C6-4EEF-8686-E541F865ED5A@gmail.com>
References: <519B743F.7040407@audifarma.com.co>
	<39946120-F3C6-4EEF-8686-E541F865ED5A@gmail.com>
List-Unsubscribe:  <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>

On Tue, May 21, 2013 at 05:28:31PM +0400, Evgeny Shishkin wrote:
> 
> On May 21, 2013, at 5:18 PM, Jeison Bedoya <jeisonb@audifarma.com.co> wrote:
> 
> > Hi people, i have a database with 400GB running in a server with 128Gb RAM, and 32 cores, and storage over SAN with fiberchannel, the problem is when i go to do a backup whit pg_dumpall take a lot of 5 hours, next i do a restore and take a lot of 17 hours, that is a normal time for that process in that machine? or i can do something to optimize the process of backup/restore.
> > 
> 
> I'd recommend you to dump with 
> 
> pg_dump --format=c
> 
> It will compress the output and later you can restore it in parallel with
> 
> pg_restore -j 32 (for example)
> 
> Right now you can not dump in parallel, wait for 9.3 release. Or may be someone will back port it to 9.2 pg_dump.
> 
> Also during restore you can speed up a little more by disabling fsync and synchronous_commit. 
> 

If you have the space and I/O capacity, avoiding the compress option will be
much faster. The current compression scheme using zlib type compression is
very CPU intensive and limits your dump rate. On a system that we have, a
dump without compression takes 20m and with compression 2h20m. The parallel
restore make a big difference as well.

Regards,
Ken


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance



view thread (6+ messages)  latest in thread

Message-ID: <20130521154613.GE12507@aart.rice.edu>
Permalink:  ../20130521154613.GE12507@aart.rice.edu/
Also on:    postgresql.org/message-id/20130521154613.GE12507@aart.rice.edu

 · 

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: ktm@rice.edu, itparanoia@gmail.com, jeisonb@audifarma.com.co
  Subject: Re: performance database for backup/restore
  In-Reply-To: <20130521154613.GE12507@aart.rice.edu>

* 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