Note: I am not certain if this is a bug in Discourse. I have tried to collect necessary evidence, and so far I have not found anything pointing to our infra/setup. Our configuration is as vanilla as as possible at Tappara.co Observed phenomenom: Chat-like rapid discussion topics stop updating auto…

We tried a game with… DISCOURSE_REJECT_MESSAGE_BUS_QUEUE_SECONDS: 0.3 DISCOURSE_MAX_REQS_PER_IP_MODE: none …and when the emotions started to warm up in the 3rd period, things got worse. We reached the limits of ours servers, users were constantly pushed to logged out - mode and the game chat was fr…

Mine is a football forum and I have experienced similar challenges. Basically what I found was it was scalable issue. The issues for me kicked in at different levels. Digital Ocean 1 CPU 1 GB = 30 -40 users in chat like situation 2 CPUs and 2 GB= 70-80 users in chat like situation 4 CPUs and …

I should also add with Hetzner test the whose online plugin didn’t make any difference. But discourse quick messages plugin seemed to be detrimental.

[Bild] sam: You can reduce rate limits, this will allow users to interact more aggressively with Discourse. Specifically you could double DISCOURSE_MAX_REQS_PER_IP_PER_MINUTE and DISCOURSE_MAX_REQS_PER_IP_PER_10_SECONDS The next game is due tomorrow. I have removed our own hacks and we are tr…

Question to @sam & other developers. How does the forever growing size of the database impact this use case, where users hammer a single topic for a couple of hours? I had a look at historical game chat activity and noticed that we had games with huge statistics back in 2017, when our server had a…

[Bild] ljpp: I also uncommented the db_work_mem 40MB line from app.yml You might try upping it to 80MB. Maybe instead of the other change.

This is one point we are actively working on all the time. When Discourse was new, almost all sites had a brand new database so the database could fit in memory easily. Now, a few years later, some sites have over 100GB databases and RAM sizes that are not even a tenth of that. One upcoming update…

@sam With these settings UX was better. Yes, there were several “chokes” and a bunch of 429’s were recorded in my Chrome inspector. CPU load was low. But then again, it was rather calm home game (many active members were on-site, not chatting). I can’t name the dials to turn but, from my rather su…

Just to rule things out, I upgraded the server to 8 vCores and 32GB RAM. I set db buffers to 16GB and Unicorns to 16. Other tweaks back to defaults. Unfortunately the upgrade did not do much. Rapid discussions are constantly freezing, even with mediocre activity. The performance is miserable nowad…

I suspect you may be hitting a Redis bottleneck, but as I said many times we can only be sure if you collect those statistics. Without it we may as well use astrology. If my suspicion is right, it will also explain that throwing more slow cores and RAM at the problem makes no difference, since Redi…

Echtzeit-Aktualisierung von Themen friert bei hoher Aktivität ein

Unterstützung

pfaffman (Jay Pfaffman) 30. Oktober 2020 um 21:59 42

Du könntest versuchen, sie auf 80MB zu erhöhen. Vielleicht statt der anderen Änderung.

Thema		Antworten	Aufrufe
Improving Instance Performance (Megatopics, Database Size and Extreme Load) Self-hosting	60	6558	13. Oktober 2020
Extreme load error Self-hosting	19	2010	13. August 2023
Topic history not loading correctly after migration Support	20	1234	8. Februar 2023
Discourse installation has been getting slower and slower and slower Self-hosting server-resources	36	2146	15. April 2023
The MEGATOPIC: public good, or public menace? Community Building	41	16847	4. April 2021

Echtzeit-Aktualisierung von Themen friert bei hoher Aktivität ein

Verwandte Themen