Hi All, So we upgraded our Centos7 Server to 2.7.0.beta4 from 2.2.2 and since then facing latency in page loading. Especially in pages with database or image contents involved. To an extent where it has become unusable. Any guidance in this regard would be much appreciated.

There is definitely something wrong with your install; you should be getting much better performance with this hardware. Try having postgres do an explicit vacuum. If you’re running the all-in-one container install: # docker exec -it -u postgres app psql discourse psql (13.1 (Debian 13.1-1.pgdg100+1)) Type "help" for help. discourse=# VACUUM ANALYZE; VACUUM How many unicorn workers do you have set in your app.yml? You can ask Discourse to set additional performance headers in responses with the following in your env section: DISCOURSE_ENABLE_PERFORMANCE_HTTP_HEADERS: true While you’re at it, you can enable miniprofiler by following this post.

[תמונה] Sirshad: This server was raised recently and is shared with 8GB RAM 10 GB of swap space. That should be quite enough. Can’t remember if it was suggested and you re-ran discourse-setup to adjust Discourse’s memory usage, or if those defaults are reasonable given whatever else is using the server. If you didn’t re-index the database after the PG13 upgrade, then you might have a look at PostgreSQL 13 update for some information about that.

Oh yes, lack of table statistics (VACUUM ANALYZE) is the most likely culprit here.

[תמונה] supermathie: While you’re at it, you can enable miniprofiler by following this post . VACUUM FULL VERBOSE; REINDEX DATABASE discourse; VACUUM VERBOSE ANALYZE; So I ran these commands and set the header in env too, but do not see much of difference in page loading time. I’m running 8 unicorns.

[תמונה] Sirshad: I’m running 8 unicorns. [hgjg] :frowning:

You ran those commands in postgres, right?

[תמונה] pfaffman: postgres Yes ran docker exec -it -u postgres app psql discoursebefore I ran the above commands.

Well, that’s all very strange. No one else has had such problems. You seem to have enough hardware. My only guess is some issue with a reverse proxy (I guess you’ve got other stuff on the machine?).

yes another docker based service. But nothing really performance intensive at all since that would have shows in the performance metrics of the machine.

Can you click on the miniprofiler icon there and show us the result?

פתרון בעיות ביצועים חמורות עם Discourse האחרון?

תמיכה התקנה

supermathie (Michael Brown) 5 באפריל,‏ 2021,‏ 4:44pm 31

Those headers are in the HTTP response for each request.

נושא		תגובות	צפיות
Could sidekiq queue be reason for 500 errors? Self-hosting server-resources	30	4427	13 ביוני,‏ 2018
Best configurations for speeding up standalone discourse Self-hosting server-resources	25	4759	14 בפברואר,‏ 2024
Sidekiq has a lot of errors and queued jobs Product Support	18	1603	1 במרץ,‏ 2024
My Discourse Jobs are stuck in queue. Not able to find solution Product Support	5	235	15 באוקטובר,‏ 2025
Unusually high CPU usage Self-hosting	31	1513	18 בפברואר,‏ 2026

פתרון בעיות ביצועים חמורות עם Discourse האחרון?

נושאים קשורים