# Discourse unavailable with high load average

**URL:** <https://meta.discourse.org/t/discourse-unavailable-with-high-load-average/96246>\
**Category:** Support\
**Created:** [September 3, 2018, 7:33am UTC](https://meta.discourse.org/t/discourse-unavailable-with-high-load-average/96246 "2018-09-03T07:33:47Z")\
**Posts on this page:** 1\
**Showing post:** 7

<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:** [September 3, 2018, 9:10am UTC](https://meta.discourse.org/t/discourse-unavailable-with-high-load-average/96246/7 "2018-09-03T09:10:01Z")

</div>

Running this many unicorn workers on two virtual cpus that already run redis and pg does not make sense.

I would run 3 workers max, and give the leftover ram to postgres.

---

_[View the full topic](https://meta.discourse.org/t/discourse-unavailable-with-high-load-average/96246)._