# Улучшение производительности инстанса (Megatopics, размер базы данных и экстремальная нагрузка)

**URL:** https://meta.discourse.org/t/improving-instance-performance-megatopics-database-size-and-extreme-load/144277
**Category:** Self-hosting
**Created:** [14.Март.2020 01:02:32 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:** 8

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [19.Март.2020 15:34:21 UTC](https://meta.discourse.org/t/improving-instance-performance-megatopics-database-size-and-extreme-load/144277/8 "2020-03-19T15:34:21Z")

</div>

> [@Парациельс](#):
>
> У нас около 80 мега-тем, которые активны постоянно (в самой крупной из них 128 тысяч сообщений).

Это крайне плохая идея, и вам следует закрыть эти темы, заменив их более мелкими тематическими или сезонными. См.

> [@The MEGATOPIC: public good, or public menace?](https://meta.discourse.org/t/the-megatopic-public-good-or-public-menace/85592):
>
> When we founded Discourse in 2013, I had the idea that we’d support topics of any length or size, from 10 replies to 100 to 10,000 to 100,000 or even more! A few years ago we ran into a technical limitation where we send down a list of all the post IDs in the topic when you enter the topic. This starts to cause problems on the client – particularly older smartphones with less memory and CPU power – at around ~10,000 replies, so we created a site setting that automatically closes topic…

---

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