From: | Ranier Vilela <ranier(dot)vf(at)gmail(dot)com> |
---|---|
To: | Sbob <sbob(at)quadratum-braccas(dot)com> |
Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org> |
Subject: | Re: significant jump in sql statement timing for on server vs a remote connection |
Date: | 2022-04-20 15:51:55 |
Message-ID: | CAEudQAoihh3A_jYVLxe8QjmRrEguOqEG+rxLtfKacT+VQ0vVXA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Em qua., 20 de abr. de 2022 às 12:16, Sbob <sbob(at)quadratum-braccas(dot)com>
escreveu:
>
> On 4/19/22 22:17, Jeff Janes wrote:
>
> On Tue, Apr 19, 2022 at 5:00 PM Sbob <sbob(at)quadratum-braccas(dot)com> wrote:
>
>>
>> However if we move the file to another server in the same network and
>> run with a psql -h then it runs for more than 10min.
>
>
> What is the ping time? Packet loss? You can't take for granted that the
> network is good and fast just because they are on the same LAN.
>
> Cheers,
>
> Jeff
>
>
> Here is the ping stats:
>
> --- db-primary ping statistics ---
> 4 packets transmitted, 4 received, 0% packet loss, time 3000ms
>
3000 ms?
Are sure that haven't packet loss?
regards,
Ranier Vilela
From | Date | Subject | |
---|---|---|---|
Next Message | wakandavision | 2022-04-20 16:35:07 | Re: Postgresql TPS Bottleneck |
Previous Message | Jeff Janes | 2022-04-20 15:49:30 | Re: Postgresql TPS Bottleneck |