> 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!
> ...
> So after all, the CPU clock speed still counts these days!
Hi Sergio,
Maybe "powerful" + "powersave"?
Maybe "powerful" + "powersave"?
as I see Sever B : Processor Base Frequency : 2.40 GHz AND Max Turbo Frequency : 3.90 GHz
Could you verify this by running the 'cpupower frequency-info' command and checking the governor line?"
read more:
"But If we haven’t emphasised it enough, firstly whatever database benchmark you are running
make sure that your CPUs are not configured to run in powersave mode."
https://www.hammerdb.com/blog/uncategorized/how-to-maximize-cpu-performance-for-postgresql-12-0-benchmarks-on-linux/
https://www.hammerdb.com/blog/uncategorized/how-to-maximize-cpu-performance-for-postgresql-12-0-benchmarks-on-linux/
regards,
Imre
Sergio Rus <geiros@xxxxxxxxx> ezt írta (időpont: 2023. máj. 31., Sze, 18:03):
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 and therefore inevitable. So after all, the CPU clock speed still counts these days! I think we're many just looking at the number of CPU cores and forgetting that the clock speed is still relevant for many tasks.I guess those simple short queries are very sensible to the hardware specs and there is no room for improving as much as the heavy queries in recent versions of Postgres, as I have seen in my tests.
