Hi Discourse Community! Recently I have been trying to improve the performance of my Discourse installation and clean up a little since my site has been growing exponentially lately. I have identified two issues, searched about them here but I don’t see a clear answer for some specifics, so I hop…

Mini-Update: Tried to tweak around the Unicorn Runners Settings but I don’t really know if there is a core-per-worker relation or is like a shared CPU kind of thing like CPU % x Second, is there a best practice for this? Also, have been reading about PostgreSQL to know how to get around that size b…

[image] Iceman: As a note we do have quite some topics with more than 10k answers , so that may be a correlation between DB Size and Performance issues? (Throwing it out, not sure). I also have some 10k+ topics, and am also seeing this message every now and then when the site is really busy.

I strongly advise you to not override the Discourse defaults, which auto-close topics with more than 10k replies. There’s a reason we have this setting on by default. :scream: Beyond that, this problem of massive post_timings table is on our radar :satellite: and we are currently brainstorming ways…

[image] codinghorror: There’s a reason we have this setting on by default. I feel like it needs a triple-confirm with the final OK button reading “I'm ok with bad things happening”. Is anyone making megatopics really work?

We have around 80 megatopics pumping the whole time (128k posts on the largest one). [image] FórumSCP A comunidade dos Sportinguistas dedicada ao Sporting Clube de Portugal onde se aborda o futebol, as modalidades e outros temas da actualidade leonina. Some 50…

[image] Paracelsus: We have around 80 megatopics pumping the whole time (128k posts on the largest one). This is a profoundly bad idea and you should shut those topics down in favor of smaller yearly or seasonal ones. See [image] The MEGATOPIC: public good, or public menace? …

I’ve got a site with a handful of >100K post mega topics. I told them that it was a mistake, but they wanted them anyway. They are complaining about performance issues. I’m hoping that I’ll soon be able to change the value back to the 10K default. It did cause me to learn some stuff about database …

[image] codinghorror: [image] Paracelsus: We have around 80 megatopics pumping the whole time (128k posts on the largest one). This is a profoundly bad idea and you should shut those topics down in favor of smaller yearly or seasonal ones. See The MEGATOPIC: public good, or public menace…

[image] Paracelsus: Imagine a topic about Trump in general or one about the United States in general. Imagine a category about Trump in general or the United States in general. No one is going to read >10000 posts in a topic straight through. They just aren’t. At some point, you can just tak…

[image] Paracelsus: Sure, it’s not impossible, but quite impracticable. OK, but my answer to this is [image] … you are opting into causing yourself considerable pain here for “reasons”.

Amélioration des performances des instances (Megatopics, taille de la base de données et charge extrême)

Soutien Installation

codinghorror (Jeff Atwood) Mars 19, 2020, 3:34 8

C’est une idée profondément mauvaise et vous devriez fermer ces topiques pour les remplacer par des topiques plus petits, annuels ou saisonniers. Voir

Sujet		Réponses	Vues
The MEGATOPIC: public good, or public menace? Community Building	41	16127	Avril 4, 2021
Real-time updating of topics freezes under high activity Support	89	7425	Février 26, 2022
Performance improvements on long topics? Support	30	5560	Août 20, 2018
Discourse installation has been getting slower and slower and slower Self-hosting server-resources	37	1742	Mai 15, 2023
PostgreSQL runaway IO Self-hosting	37	3097	Mars 17, 2021

Amélioration des performances des instances (Megatopics, taille de la base de données et charge extrême)

Sujets connexes