# Improving Instance Performance (Megatopics, Database Size and Extreme Load)

**URL:** <https://meta.discourse.org/t/improving-instance-performance-megatopics-database-size-and-extreme-load/144277>\
**Category:** Self-hosting\
**Created:** [14 maart 2020 om 01:02 UTC](https://meta.discourse.org/t/improving-instance-performance-megatopics-database-size-and-extreme-load/144277 "2020-03-14T01:02:32Z")\
**Posts on this page:** 1\
**Showing post:** 49

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [28 september 2020 om 04:45 UTC](https://meta.discourse.org/t/improving-instance-performance-megatopics-database-size-and-extreme-load/144277/49 "2020-09-28T04:45:13Z")

</div>

> [@ljpp](#):
>
> What lead me suspecting the backend, is the fact that we have been running these game chats for years, and I have not seen this “choking” before.

We have a TODO on our backlog now to improve performance for cases where 1000 people are looking at the same topic and one person posts.

As designed today we publish to all 1000 people “Hi, there is a new post for this topic” then all 1000 head to the server (mostly at the same time) asking … “hey, what is this new topic you are asking for”

We are going to look at minimally rate limiting this in a cleaner way so clients don’t hammer the server, but there are a bunch of optmisations we can make for this outlier case.

---

_[View the full topic](https://meta.discourse.org/t/improving-instance-performance-megatopics-database-size-and-extreme-load/144277)._
