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…

[이미지] 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_antenna: and we are currently brainstorm…

[이미지] 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). [이미지] 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 502…

[이미지] 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 mena…

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 …

[이미지] codinghorror: [이미지] 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? …

[이미지] 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 take …

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

인스턴스 성능 개선 (메가토픽, 데이터베이스 크기 및 극단적 부하)

제품 지원 자체 호스팅

codinghorror (Jeff Atwood) 3월 19, 2020, 3:34오후 8

이것은 매우 나쁜 아이디어이며, 더 작은 연도별 또는 계절별 토픽으로 전환하기 위해 해당 토픽들을 종료해야 합니다. 참고할 내용:

글		댓글	조회수
The MEGATOPIC: public good, or public menace? Community Building	41	16908	4월 4, 2021
Real-time updating of topics freezes under high activity Product Support	89	8879	2월 26, 2022
Performance improvements on long topics? Product Support	29	5855	7월 12, 2018
Discourse installation has been getting slower and slower and slower Self-hosting server-resources	36	2201	4월 15, 2023
PostgreSQL runaway IO Self-hosting	35	3739	3월 3, 2021

인스턴스 성능 개선 (메가토픽, 데이터베이스 크기 및 극단적 부하)

Related topics