From: | David Wall <d(dot)wall(at)computer(dot)org> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_dump slower than pg_restore |
Date: | 2014-07-04 05:43:59 |
Message-ID: | 53B63F1F.7040209@computer.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 7/3/2014 10:13 PM, Bosco Rama wrote:
> Is the issue with S3 or just transfer time? I would expect that
> 'rsync' with the '--partial' option (or -P if you want progress info
> too) may help there.
Don't know if rsync and S3 work together or what that would mean, but
it's not an issue I'm suffering now. I do think they may now have a
multipart upload with s3cmd (which I use), though that also wasn't
available when we first built our scripts.
I suspect nothing is really helping here and I'm mostly limited by disk
I/O, but not sure why the pg_dump is so much slower than pg_restore as
they are all on the same disks. I say this because even with pg_dump
-Z0 | gpg -z 0 and gzip removed entirely and no --oids on pg_dump,
there's no effective difference in overall speed. While I can see all
of those processes vying for resources via 'top -c', the throughput
remains much the same.
From | Date | Subject | |
---|---|---|---|
Next Message | David Wall | 2014-07-04 05:51:29 | Re: pg_dump slower than pg_restore |
Previous Message | Bosco Rama | 2014-07-04 05:13:25 | Re: pg_dump slower than pg_restore |