Unlocking high-performance PostgreSQL with key memory optimizations

https://stormatics.tech/blogs/unlocking-high-performance-postgresql-key-memory-optimizations

by camille_134 • 6 months ago

97 8 6 months ago

stormatics.tech

tehlike• 6 months ago

I generally use this: https://pgtune.leopard.in.ua/

arkh• 6 months ago

Yup, I was expecting pgtune being mentioned in the article.

And maybe something like HammerDB to check performances.

fix4fun• 6 months ago

Nice tool. Do you know maybe similar tool for MySQL ?

qeternity2• 6 months ago

Does not instill confidence when the queries they provide don't work.

For anyone curious, the corrected query:

SELECT sum(blks_hit)::numeric / nullif(sum(blks_hit + blks_read), 0) AS cache_hit_ratio FROM pg_stat_database;

itiswatitis• 6 months ago

I just ran their query, and it works

qeternity2• 6 months ago

It does not in PG17.

HackerThemAll• 6 months ago

"How do we size shared_buffers? A common starting rule of thumb is:"

I have an improved rule of thumb:

Give a lot of RAM. Give it all the RAM you can. And then buy some more and also give it to shared_buffers. Buffering data in RAM/CPU cache is crucial for performance.

Unlocking high-performance PostgreSQL with key memory optimizations

Related Stories