Re: design for parallel backup - Mailing list pgsql-hackers

From Robert Haas
Subject Re: design for parallel backup
Date
Msg-id CA+TgmoZccXE56j4sg2RhOT3XgHXTZNOKVbzKUQgx5PNkJH3tNA@mail.gmail.com
Whole thread Raw
In response to Re: design for parallel backup  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
On Wed, Apr 22, 2020 at 12:20 PM Peter Eisentraut
<peter.eisentraut@2ndquadrant.com> wrote:
> On 2020-04-20 22:36, Robert Haas wrote:
> > My suspicion is that it has mostly to do with adequately utilizing the
> > hardware resources on the server side. If you are network-constrained,
> > adding more connections won't help, unless there's something shaping
> > the traffic which can be gamed by having multiple connections.
>
> This is a thing.  See "long fat network" and "bandwidth-delay product"
> (https://en.wikipedia.org/wiki/Bandwidth-delay_product).  The proper way
> to address this is presumably with TCP parameter tuning, but in practice
> it's often easier to just start multiple connections, for example, when
> doing a backup via rsync.

Very interesting -- thanks!

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: backup manifests
Next
From: Robert Haas
Date:
Subject: Re: Do we need to handle orphaned prepared transactions in the server?