| From: | Rui DeSousa <rui(dot)desousa(at)icloud(dot)com> |
|---|---|
| To: | Karthik Yellapragada <karthik(dot)yellapragada(at)gmail(dot)com> |
| Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Parallelize WAL Sender and WAL receiver |
| Date: | 2024-09-05 04:33:10 |
| Message-ID: | 8805E20A-38B7-4D13-AB8C-95992471C4AD@icloud.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> On Sep 4, 2024, at 11:47 PM, Karthik Yellapragada <karthik(dot)yellapragada(at)gmail(dot)com> wrote:
>
> Appreciate the responses, the network is good.. around 350 MB/s between prinary and secondary, both primary and secondary in the same DC. And it’s ASYC replication..
>
> I see the issue when the writes are super heavy ,
> I am only thinking if we can add more processes that sends / receives the WALs , we can speed up the transfer rate of WALs to the secondary..
>
> I understand the Apply can not be parallelized..
Sounds like you have 10GbE between the nodes? Are you sure it’s send rate? If so, I would look at the disk subsystem.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Achilleas Mantzios - cloud | 2024-09-05 07:13:10 | postgresql FDW vs dblink for DDL |
| Previous Message | Karthik Yellapragada | 2024-09-05 03:47:40 | Re: Parallelize WAL Sender and WAL receiver |