# Topics over 10,000 posts remove "Frequent Posters"

**URL:** https://meta.discourse.org/t/topics-over-10-000-posts-remove-frequent-posters/107671
**Category:** Support
**Created:** [January 27, 2019, 11:33pm UTC](https://meta.discourse.org/t/topics-over-10-000-posts-remove-frequent-posters/107671 "2019-01-27T23:33:41Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![orangeandblack5](https://avatars.discourse-cdn.com/v4/letter/o/edb3f5/32.png) [@orangeandblack5](https://meta.discourse.org/u/orangeandblack5)
#### Post date: [January 28, 2019, 4:56pm UTC](https://meta.discourse.org/t/topics-over-10-000-posts-remove-frequent-posters/107671/5 "2019-01-28T16:56:07Z")

</div>

> [@The MEGATOPIC: public good, or public menace?](https://meta.discourse.org/t/the-megatopic-public-good-or-public-menace/85592/1):
>
> we send down a list of all the post IDs in the topic when you enter the topic

Would it not make more sense to just cache data such as the number of posts per user server-side for larger topics so users don’t need to poll every post in a topic once you reach 10,000 posts?

Or is there some reason simply storing this kind of data in one batch and altering it serverside as each new post is made rather than actively polling every single post each time you load the topic doesn’t work?

Is that a byproduct of having the ability to jump everywhere within a topic, so needing to be able to pull up any post at a given time?

And, if so, would not enabling pages make sense for large topics?

Or am I fundamentally off target somewhere?

Thanks!

---

_[View the full topic](https://meta.discourse.org/t/topics-over-10-000-posts-remove-frequent-posters/107671)._