Em qua., 31 de mai. de 2023 às 09:40, Sergio Rus
escreveu:
> As you can see, server B has 2 CPUs and is using NUMA on Linux. And the
> CPU clock is slower on server B than server A. Maybe any of those are
> causing that latency?
>
> Any suggestions or ideas where to look? I'd really appreciate
Hi,
On 2023-05-31 14:40:05 +0200, Sergio Rus wrote:
> I've been configuring a new server and tuning Postgresql 15.3, but I'm
> struggling with a latency I'm consistently seeing with this new server when
> running fast short queries, compared to the other server.
>
> We're running two different
> Server B is the new server and is way more powerful than server A:
> ...
> So after all, the CPU clock speed still counts these days!
Hi Sergio,
Maybe "powerful" + "powersave"?
as I see Sever B : Processor Base Frequency : 2.40 GHz AND
* Max Turbo Frequency : 3.90 GHz*
Could you verify
Thanks for your reply, Ken.
With such a big server I was convinced that we should see a boost
everywhere, but after spending so much time tweaking and looking at so many
parameters on Linux, Postgresql and our current setup, I started to think
that maybe that latency was intrinsic to the hardware
On Wed, May 31, 2023 at 02:40:05PM +0200, Sergio Rus wrote:
> Hi guys,
>
> I've been configuring a new server and tuning Postgresql 15.3, but I'm
> struggling with a latency I'm consistently seeing with this new server when
> running fast short queries, compared to the other server.
>
> We're
Hi guys,
I've been configuring a new server and tuning Postgresql 15.3, but I'm
struggling with a latency I'm consistently seeing with this new server when
running fast short queries, compared to the other server.
We're running two different versions of Postgresql:
- Server A: Postgresql 9.3
-
Wow Michael you are absolutely right. Turning jit off results in a query
execution about twice as fast as pg11. That is a huge relief. I will read
the jit related docs and see if there is anything smarter I should be doing
other than disabling jit entirely, but it works a treat for this query.
>
> Does anyone have a theory of why pg15 should behave so differently to pg11
> here? Better still, any suggestions for configuration that might make pg15
> behave more like pg10. I am really dreading the prospect of stepping our
> many live implementations back to pg11 :-(.
>
One major factor
Hello
We have an application (https://dhis2.org) which has been using postgresql
as a backend for the past 15 years or so. Gradually moving through pg
versions 8,9,10 etc as the years went by. At the moment a large number of
our implementations are using versions 13, 14 and 15. Unfortunately
