In an effort to update our Forum I did a fresh VPS install + Restore on the weekend. This was going to solve multiple issues for us: Renew outdated ubuntu Update Discourse Upgrade to Postgres 15 While generally things went fine I saw issues coming up afterwards with Postgres processes going wild…

Right now it’s only one sidekiq task running with “Jobs::BackfillBadge” but still 7 postgres processes are seemingly blocking 100% cpu constantly. Really curious what’s going on there. [Screenshot 2025-02-17 @ 14.59.12@2x]

[изображение] Helmi: I did a fresh VPS install + Restore on the weekend. After such moves it is a good idea to run a vacuum for database stats.

How much ram and cpu do you have? How much memory do you give postgres?

That test serer is on 32GB, 16 core, config is set to 64MB work mem. EDIT: Shared buffers are at 8GB Currently doing a vaccuum which looks stuck [Screenshot 2025-02-17 @ 17.00.32@2x] Not sure if it’s doing something but it’s been there for 30+ minutes already. I did put the forum to read only …

You really don’t want to run a vacuum full. All you need to get performance back is a VACUUM VERBOSE ANALYZE. You can’t run a FULL in a running site.

I’m not expert at huge databases, but I’d make the buffers two or three times that. I’m sure you have indexes that are 8gb

[изображение] Jay Pfaffman: I’m not expert at huge databases, but I’d make the buffers two or three times that. :thinking: Postgres recommends never setting shared_buffers over 40% of the internal memory? That said, [изображение] Helmi: our database is quite huge - we’re at around 150gb…

[изображение] Richard - Communiteq: Postgres recommends never setting shared_buffers over 40% of the internal memory? Aha! Sensible advice from an expert! So maybe I was right that 8GB/25% isn’t enough, and though 16GB is more than 40%, it might still be a good suggestion because . . . . […

Guys. as said this is a test server - there is no traffic on it. This server definitely isn’t good enough for production use but that’s not the issue here. The question is why we do see postgres processes sticking like that (with 100% CPU usage) and slowing down things drastically. We were running t…

Бесконечно работающие процессы Postgres и низкая производительность после переустановки/восстановления

Поддержка

Falco (Falco) 17.Февраль.2025 14:08:31 3

After such moves it is a good idea to run a vacuum for database stats.

1 лайк

Тема		Ответов	Просм.
Slow Sidekiq + Postmaster using 95%+ CPU (32 cores) after Postgresql Version Upgrade Self-hosting server-resources	23	3043	28.06.2020
Postgres using 100% of CPU Self-hosting server-resources	18	20076	10.04.2021
Post 3.5.1 update - CPU maxed out 100% Support	5	120	04.02.2025
Primary Postgres database process (postmaster) eating all CPU Self-hosting server-resources	13	4127	28.05.2020
Server load issues (after rebuild hanged) Self-hosting	4	221	19.05.2024

Бесконечно работающие процессы Postgres и низкая производительность после переустановки/восстановления

Связанные темы