# Huge useful topics optimization

**URL:** https://meta.discourse.org/t/huge-useful-topics-optimization/200566
**Category:** Feature
**Created:** [August 16, 2021, 9:01am UTC](https://meta.discourse.org/t/huge-useful-topics-optimization/200566 "2021-08-16T09:01:21Z")
**Posts on this page:** 1
**Showing post:** 2

<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: [January 17, 2022, 10:27pm UTC](https://meta.discourse.org/t/huge-useful-topics-optimization/200566/2 "2022-01-17T22:27:19Z")

</div>

See

> [@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…

The only real solution here is **strict moderation** to avoid megatopics.

---

_[View the full topic](https://meta.discourse.org/t/huge-useful-topics-optimization/200566)._