pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feed From: Scott Ribe <scott_ribe@elevated-dev.com>
To: Jean-Armel Luce <jaluce06@gmail.com>
Cc: Cédric Villemain <cedric.villemain.debian@gmail.com>
Cc: [ADMIN] <pgsql-admin@postgresql.org>
Subject: Re: rsync and streaming replication
Date: Thu, 17 Nov 2011 10:45:10 -0700
Message-ID: <B2C15563-E31A-41A8-AE9A-5F2D65097362@elevated-dev.com> (raw )
In-Reply-To: <CALnckSoXuUPH=FT4TCf+FBcs0Sw7wYDFqPQ18VvwTkVedNs7BA@mail.gmail.com >
References: <CALnckSpEi-6JjfEFLUcp13nScHbbcywFcmhn51iK2sj_eXbEkQ@mail.gmail.com >
<87pqgxf8p9.fsf@comcast.net >
<CALnckSqDpZi=_w8XckMLBHu_V4kgtn+EqNsqFcNgLtbcYorzDA@mail.gmail.com >
<CAF6yO=0UEB82UP2Lusd2xfrY+7TyVpn9pcFdDv1=_w9Rf=FqXg@mail.gmail.com >
<CALnckSqdG0aQ09nUhUeGWZ8SC8J25WEHHe4wD0jnz7K2+Kov5A@mail.gmail.com >
<639B3C52-BF6D-4CE9-A710-75D369E9607E@elevated-dev.com >
<CAF6yO=3WQMsa5WQkHNbfW9URnto5M94U5U9ZEQ3LS=dLRri2dw@mail.gmail.com >
<39A965E0-DE37-41F3-8D69-321419BB8B09@elevated-dev.com >
<CAF6yO=2Cm_1sq7PZ=xRp5t+Oxu3e+bFWiRX+V2TOce4b5kauKg@mail.gmail.com >
<640CEEBE-CB12-4FC9-9758-0319A49E7ACF@elevated-dev.com >
<CALnckSqLVWff3x98k1sZcg09G8ARScQUPZPGkZ0ve1HjiFS6jw@mail.gmail.com >
<CAF6yO=3G-P0KgSH=Eiqw3Se38Civ7QktKF8q2-Zs0Rgy47=6Ww@mail.gmail.com >
<CALnckSp2Ygt7nJBwBX1gRkf6c7ZbEFHS=ydrLsn4cB79Yx_gvw@mail.gmail.com >
<CAF6yO=3fjuokv9J80oW9oQWF9YdYxMcH_gSyfJ5KCKwiA5V_5w@mail.gmail.com >
<CALnckSqvM7HrzBK2ETaDQh6OotRLZF=_enJvDfZ0wQZMoHMaHg@mail.gmail.com >
<48B4CE29-7776-4D7A-8A A5-D45A4F77BB75@elevated-dev.com >
<CAF6yO=3XQurt1RfJwVpaq2Ea_NpQoq9L8ayP4AxPgQ4Vo5fFEA@mail.gmail.com >
<CALnckSoXuUPH=FT4TCf+FBcs0Sw7wYDFqPQ18VvwTkVedNs7BA@mail.gmail.com >
On Nov 17, 2011, at 10:11 AM, Jean-Armel Luce wrote:
> > Also, I believe you said -z seemed to slow it down?
> I confirm
Is there a lot of your data that is already compressed? Either something like images which you are storing as bytea or large objects? Or long text values that pg will itself compress out of line?
> Today, I tried with command : rsync -rc --block-size=8192
> Rsync duration with blksize=8192 was 31 minutes (yesterday without blocksize, duration was 32 minutes exactly)
That seems not too bad, in that you're sustaining >3GB/min of reading & checksumming. (Some of my earlier comments were based on the belief that your db was 20GB.)
--
Scott Ribe
scott_ribe@elevated-dev.com
http://www.elevated-dev.com/
(303) 722-0567 voice
view thread (26+ messages) latest in thread
Message-ID: <B2C15563-E31A-41A8-AE9A-5F2D65097362@elevated-dev.com>
Permalink: ../B2C15563-E31A-41A8-AE9A-5F2D65097362@elevated-dev.com/
Also on: postgresql.org/message-id/B2C15563-E31A-41A8-AE9A-5F2D65097362@elevated-dev.com
copy link · copy postgr.es
reply 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-admin@postgresql.org
Cc: scott_ribe@elevated-dev.com, jaluce06@gmail.com, cedric.villemain.debian@gmail.com
Subject: Re: rsync and streaming replication
In-Reply-To: <B2C15563-E31A-41A8-AE9A-5F2D65097362@elevated-dev.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