| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Don Seiler <don(at)seiler(dot)us>, Rui DeSousa <rui(dot)desousa(at)icloud(dot)com> |
| Cc: | Johannes Truschnigg <johannes(at)truschnigg(dot)info>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Streaming Replication Networking Best Practices? |
| Date: | 2018-05-14 20:33:36 |
| Message-ID: | 9882daba-b884-a17f-0437-d2041961d025@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On 5/14/18 16:22, Don Seiler wrote:
> On Mon, May 14, 2018 at 2:53 PM, Rui DeSousa <rui(dot)desousa(at)icloud(dot)com
> <mailto:rui(dot)desousa(at)icloud(dot)com>> wrote:
>
> What is the latency between the two sites? That is going to dictate
> how much potential throughput a given TCP/IP stream could use. You
> may need tune your TCP/IP window to increase the throughput.
>
>
> Ping shows a pretty solid latency of 49-50 ms.
You might find that increasing the TCP receive buffer on the receiving
side will help.
Here is a bit of an explanation:
https://stackoverflow.com/questions/259553/tcp-is-it-possible-to-achieve-higher-transfer-rate-with-multiple-connections
I believe this mechanism is the reason (or at least one of them) why
using parallel rsync (for base backup) or parallel copying of archive
segments is sometime faster than straight streaming.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rui DeSousa | 2018-05-14 21:02:47 | Re: Streaming Replication Networking Best Practices? |
| Previous Message | Don Seiler | 2018-05-14 20:22:08 | Re: Streaming Replication Networking Best Practices? |