# 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:** [March 14, 2020, 1:02am 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:** 14

<div class="post-metadata">

### Author: ![Paracelsus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/paracelsus/32/164912_2.png) [@Paracelsus](https://meta.discourse.org/u/Paracelsus)
#### Post date: [March 20, 2020, 7:29pm UTC](https://meta.discourse.org/t/improving-instance-performance-megatopics-database-size-and-extreme-load/144277/14 "2020-03-20T19:29:41Z")

</div>

👍

I believe you guys, it’s just that our users are used like this and it’ll take a bit of effort to get there… but it’s doable.

Related to this, I was just reading @codinghorror post [Natural breakpoints or "chapters" for long topics? - #53 by codinghorror](https://meta.discourse.org/t/natural-breakpoints-or-chapters-for-long-topics/16461/53) and thought that this kind of table of contents but for topics only would be a nice solution to be able to gather and have visible a sequence of topics while browsing and replying only in a single one.

---

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