| From: | Ranier Vilela <ranier(dot)vf(at)gmail(dot)com> |
|---|---|
| To: | Ayub Khan <ayub(dot)hp(at)gmail(dot)com> |
| Cc: | Pgsql Performance <pgsql-performance(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: waiting for client write |
| Date: | 2021-06-11 18:25:04 |
| Message-ID: | CAEudQArU7KnZmZYXb2AT2-Y0V_9aFyMMMAaMXFYdWcFLjSaBdQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Em sex., 11 de jun. de 2021 às 15:19, Ayub Khan <ayub(dot)hp(at)gmail(dot)com>
escreveu:
> Ranier,
>
> I verified the link you gave and also checked AWS documentation and found
> the exact output as shown in AWS:
>
> https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/network_mtu.html
>
> [ec2-user ~]$ tracepath amazon.com
> 1?: [LOCALHOST] pmtu 9001
> 1: ip-xxx-xx-xx-1.us-west-1.compute.internal (xxx.xx.xx.x) 0.187ms pmtu 1500
>
> Should the LOCALHOST pmtu needs to be updated to 1500 ?
>
> Or us-west-1.compute.internal should be set to 9000.
I think both must match. 9000 are jumbo frames.
The bigger the better.
Try switching to 9000 first and 1500 if it does not work.
regards,
Ranier Vilela
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ayub Khan | 2021-06-11 19:45:27 | Re: waiting for client write |
| Previous Message | Ayub Khan | 2021-06-11 18:19:19 | Re: waiting for client write |