# PostgreSQL runaway IO

**URL:** https://meta.discourse.org/t/postgresql-runaway-io/91516
**Category:** Self-hosting
**Created:** [July 3, 2018, 9:59pm UTC](https://meta.discourse.org/t/postgresql-runaway-io/91516 "2018-07-03T21:59:01Z")
**Posts on this page:** 1
**Showing post:** 16

<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: [July 5, 2018, 12:58am UTC](https://meta.discourse.org/t/postgresql-runaway-io/91516/16 "2018-07-05T00:58:11Z")

</div>

> [@codinghorror](#):
>
> Surprising that you are running into this with 17k posts in one topic, I view 20k as the “starting to be a problem” cutoff. But maybe we should set the bar lower cc

I have mentioned this particular issue before… it is totally unrelated to @tgxworld’s work.

> [@Reschedule sidekiq scheduled job](https://meta.discourse.org/t/reschedule-sidekiq-scheduled-job/90805/9):
>
> If we give up the requirement for a gemetric mean of read time on every post on large topics, we can make the job much faster and then its a lot less likely to kill his system at 3AM. In theory that code should work, my guess is that it is writing it to the wrong part of redis, you want to be at the default site of the multisite.

I am still not buying that we are getting any value from “geometric mean of all read times for all posts”… a simple… which posts are read most is probably good enough for the “best of” algorithm.

Plus this whole concept is a bit broken imo cause the further you get to the end of a topic the less people read it.

I think a **simple** fix here, is to stop doing the whole geometric mean read time thing on topics with more than say 1000 posts. Which is oddly the only time we would use it… ☹

---

_[View the full topic](https://meta.discourse.org/t/postgresql-runaway-io/91516)._