# Forum Unusable due to "Can’t save in background: fork: Cannot allocate memory”

**URL:** <https://meta.discourse.org/t/forum-unusable-due-to-can-t-save-in-background-fork-cannot-allocate-memory/57781>\
**Category:** Self-hosting\
**Created:** [22 בפברואר,‏ 2017,‏ 12:17pm UTC](https://meta.discourse.org/t/forum-unusable-due-to-can-t-save-in-background-fork-cannot-allocate-memory/57781 "2017-02-22T12:17:56Z")\
**Posts on this page:** 1\
**Showing post:** 6

<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:** [23 בפברואר,‏ 2017,‏ 1:19am UTC](https://meta.discourse.org/t/forum-unusable-due-to-can-t-save-in-background-fork-cannot-allocate-memory/57781/6 "2017-02-23T01:19:16Z")

</div>

Even 1GB works fine, _provided you have 2GB of swap_, over a series of years running Discourse.

There are sometimes brief periods (usually during upgrades; it is strange to hear about this during regular use) where memory needs to be a bit larger.

It is definitely interesting to hear that no swap at all is affecting 2GB RAM instances cc @sam

---

_[View the full topic](https://meta.discourse.org/t/forum-unusable-due-to-can-t-save-in-background-fork-cannot-allocate-memory/57781)._
