| From: | Joachim Wieland <joe(at)mcknight(dot)de> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: parallel pg_dump |
| Date: | 2012-04-05 10:32:07 |
| Message-ID: | CACw0+124dNPZfoN5NQVgFVEmbq+g-EvT_c_2+nr6S0eEuh7zvQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
So here's a pg_dump benchmark from a real world database as requested
earlier. This is a ~750 GB large 9.0.6 database, and the backup has
been done over the internal network from a different machine. Both
machines run Linux.
I am attaching a chart that shows the table size distribution of the
largest tables and the overall pg_dump runtime. The resulting (zlib
compressed) dump directory was 28 GB.
Here are the raw numbers:
-Fc dump
real 168m58.005s
user 146m29.175s
sys 7m1.113s
-j 2
real 90m6.152s
user 155m23.887s
sys 15m15.521s
-j 3
real 61m5.787s
user 155m33.118s
sys 13m24.618s
-j 4
real 44m16.757s
user 155m25.917s
sys 13m13.599s
-j 6
real 36m11.743s
user 156m30.794s
sys 12m39.029s
-j 8
real 36m16.662s
user 154m37.495s
sys 11m47.141s
| Attachment | Content-Type | Size |
|---|---|---|
| pg_dump_benchmark.pdf | application/pdf | 77.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2012-04-05 10:46:39 | Re: poll: CHECK TRIGGER? |
| Previous Message | Simon Riggs | 2012-04-05 09:41:08 | Re: patch: improve SLRU replacement algorithm |