From: Shaun Thomas <sthomas@optionshouse.com>
To: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Performance of pg_basebackup
Date: Tue, 12 Jun 2012 09:54:28 -0500
Message-ID: <4FD75824.9000005@optionshouse.com> (raw)
Hey everyone,
I was wondering if anyone has found a way to get pg_basebackup to be...
faster. Currently we do our backups something like this:
tar -c -I pigz -f /db/backup_yyyy-mm-dd.tar.gz -C /db pgdata
Which basically calls pigz to do parallel compression because with RAIDs
and ioDrives all over the place, it's the compression that's the
bottleneck. Otherwise, only one of our 24 CPUs is actually doing anything.
I can't seem to find anything like this for pg_basebackup. It just uses
its internal compression method. I could see this being the case for
pg_dump, but pg_basebackup just produces regular tar.gz files. Is there
any way to either fake a parallel compression here, or should this be a
feature request for pg_basebackup?
--
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604
312-444-8534
sthomas@optionshouse.com
______________________________________________
See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email
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: sthomas@optionshouse.com
Subject: Re: Performance of pg_basebackup
In-Reply-To: <4FD75824.9000005@optionshouse.com>
* 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