# 1gb warning is too course grained

**URL:** https://meta.discourse.org/t/1gb-warning-is-too-course-grained/114721
**Category:** Self-hosting
**Created:** [April 11, 2019, 3:50am UTC](https://meta.discourse.org/t/1gb-warning-is-too-course-grained/114721 "2019-04-11T03:50:27Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![jamesh](https://avatars.discourse-cdn.com/v4/letter/j/3d9bf3/32.png) [@jamesh](https://meta.discourse.org/u/jamesh)
#### Post date: [April 11, 2019, 3:50am UTC](https://meta.discourse.org/t/1gb-warning-is-too-course-grained/114721/1 "2019-04-11T03:50:27Z")

</div>

We’re running 2xt3.micros (AWS 1gb VPS) as web only discourse instances, and separate postgres and redis boxes (i.e. 4gb of RAM total), but discourse is very keen to spam me that I have insufficient memory, since on a single instance (even though there’s nothing else running!) I have slightly under 1\_000\_000 bytes (and so ram\_check triggers the memory\_warning message). I could scale this out forever, reduce sidekiq to 0 and unicorn workers to 1, and discourse would still be telling me that…

A trivial fix would be to change 1\_000\_000 to something like 950\_000. Perhaps a better fix would be to only emit the warning if its running on the same host as the database, and disable it otherwise (since if you’ve split them, you’re presumably controlling your own destiny…).

---

<div class="post-metadata">

### Author: ![jamesh](https://avatars.discourse-cdn.com/v4/letter/j/3d9bf3/32.png) [@jamesh](https://meta.discourse.org/u/jamesh)
#### Post date: [April 11, 2019, 3:51am UTC](https://meta.discourse.org/t/1gb-warning-is-too-course-grained/114721/2 "2019-04-11T03:51:12Z")

</div>

I can understand if you don’t care too much about this, but would you accept the trivial PR? (changing 1\_000\_000 to 950\_000?)

---

<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: [April 11, 2019, 7:40am UTC](https://meta.discourse.org/t/1gb-warning-is-too-course-grained/114721/3 "2019-04-11T07:40:09Z")

</div>

Sounds OK to me at least.

---

<div class="post-metadata">

### Author: ![jamesh](https://avatars.discourse-cdn.com/v4/letter/j/3d9bf3/32.png) [@jamesh](https://meta.discourse.org/u/jamesh)
#### Post date: [April 11, 2019, 11:36pm UTC](https://meta.discourse.org/t/1gb-warning-is-too-course-grained/114721/4 "2019-04-11T23:36:59Z")

</div>

> <https://github.com/discourse/discourse/pull/7368>
>
> When you have '1gb' RAM, this might be a little less than 1,000,000.
> Let's not …warn unless it's well under 1gb.

---

<div class="post-metadata">

### Author: ![zogstrip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/zogstrip/32/512781_2.png) [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [April 26, 2019, 2:31pm UTC](https://meta.discourse.org/t/1gb-warning-is-too-course-grained/114721/5 "2019-04-26T14:31:13Z")

</div>


