Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id CBA66FD3E1E for ; Tue, 12 Jun 2012 11:54:49 -0300 (ADT) Received: from smtp2.peak6.com ([38.98.137.9]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SeSUY-0001Rt-KJ for pgsql-performance@postgresql.org; Tue, 12 Jun 2012 14:54:48 +0000 X-AuditID: 0a02cb1e-b7fa76d000000a63-16-4fd758046e16 Message-ID: <4FD75824.9000005@optionshouse.com> Date: Tue, 12 Jun 2012 09:54:28 -0500 From: Shaun Thomas Reply-To: Organization: Peak6 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 MIME-Version: 1.0 To: "pgsql-performance@postgresql.org" Subject: Performance of pg_basebackup Content-Type: text/plain; charset="ISO-8859-1"; format=flowed content-transfer-encoding: 7bit X-Originating-IP: [10.10.201.64] X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrAIsWRmVeSWpSXmKPExsXClcIrpssacd3f4MkpdovrM88xOzB6XNg3 jT2AMaqB0SYxLy+/JLEkVSEltTjZVsm/oCQzP6/YI7+0OFXBJbM4OScxMze1SEkhM8VWyVxJ oSAnMTk1NzWvxFYpsaAgNS9FyY5LAQPYAJVl5imk5iXnp2TmpdsqeQb761pYmFrqGirZxSOD hE6WjJb1kxgL/rFVbOnUbmC8wNrFyMkhIWAi0bJ6MxuELSZx4d56MJtXQF/i7L8pLCA2i4Cq xNstmxlBbDYBXYlJ/SvAaoQEVCT6zt5gArH5BYQl9n1oYgaxRQVCJM49+Q41R1Di5MwnYHNE BDwlZu/fBmYLA83sWzQPzGYWsJW4MOc6lC0vsf3tHGaI+aoSK5onQt2mIPH/yjumCYz8s5CM nYWkfRaS9gWMzKsYxYvLEpMzMs0KinNLCgz1ClITs8308lJLNjGCYovptNwOxhUXFA8xCnAw KvHwCqhc8xdiTSwrrsw9xCjBwawkwqsfdt1fiDclsbIqtSg/vqg0J7X4EKMpMDwmMkuJJucD 4z6vJN7Q2NDS1NLEzNLc2NhASZz3+9oz/kIC6cCYzk5NLUgtgulj4uCUamCMiLjwq5TjZab4 rY+Su139qhp8+00r+/32L6zYfOvqWsP5LU+/rpvBcWX5tQ59TlkTlT1vtoQH7zPgKrDzuMXK pGscfnV1qRWv3c2PSYJSvVMmH+7fozBBXXuh19H6dZeLJwtNdOm5xLKVOyR9KZPBZC4bO90N Ck6HY5p/zjzpcuatt25kQqQSS3FGoqEWc1FxIgAugZhuwwIAAA== X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201206/69 X-Sequence-Number: 47095 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