On 10/19/2012 09:44 AM, Karl Denninger wrote:
For really BIG databases (as opposed to moderately-big) this could be a much-more material problem than it is for me.
Which reminds me. I really wish pg_basebackup let you specify an alternative compression handler. We've been using pigz on our systems because our database is so large. It cuts backup time drastically, from about 2.5 hours to 28 minutes.
Until a CPU can compress at the same speed it can read data from disk devices, that's going to continue to be a problem. Parallel compression is great.
So even after our recent upgrade, we've kept using our home-grown backup system. :(
-- Shaun Thomas OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604 312-444-8534 sthomas@xxxxxxxxxxxxxxxx ______________________________________________ See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
