From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Optimize streaming replication because of network latency
Date: Thu, 10 Dec 2020 12:00:27 -0600
Message-ID: <b4d8431d-b877-0a69-f85b-d37acd4b0d3a@gmail.com> (raw)
In-Reply-To: <99AA0D0E-E266-48AF-AB29-4E2B73CBE3EA@webedia-group.com>
References: <99AA0D0E-E266-48AF-AB29-4E2B73CBE3EA@webedia-group.com>
On 12/10/20 11:41 AM, Mai Peng wrote:
> Hello,
>
> We’ve added a streaming standby on a gcp container. There’s a lot of
> network latency between our primary in EU and this standby in South America.
> I did a big update on a table ( 4 millions rows) and it generates a lot of
> lag : more than 5 hours.
> The standby has great hardware ressources: cpu, ssd disk and had no load
> during this update.
> How could we handle this lag and have less impact, less lag ?
How effectively fast is the pipe between the two servers? Where are the
bottlenecks? Is the pipe shared by other users?
> Basic PG Config:
> shared_buffers = 8GB
> work_mem = 128MB
> max_connections = 600
> wal_keep_segments = 1000
> wal_sender_timeout = 0
> replication_timeout=(not set)
> wal_receiver_status_interval=10s
> max_wal_senders=20
> Checkpoint_timeout = 10min
> Max_wal_size= 2GB
> min_wal_size= 1GB
>
>
> Thank you
> Mai
--
Angular momentum makes the world go 'round.
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: ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: Optimize streaming replication because of network latency
In-Reply-To: <b4d8431d-b877-0a69-f85b-d37acd4b0d3a@gmail.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