# 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:** 9

<div class="post-metadata">

**Author:** ![Iceman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/iceman/32/181309_2.png) [@Iceman](https://meta.discourse.org/u/Iceman)\
**Post date:** [10 בנובמבר,‏ 2017,‏ 11:06pm UTC](https://meta.discourse.org/t/forum-unusable-due-to-can-t-save-in-background-fork-cannot-allocate-memory/57781/9 "2017-11-10T23:06:12Z")

</div>

Hi,

Sorry to bring this up from Februrary but whanted to ask if it’s normal to have intermittent Error 500 with ~80% memory usage (like the OP).

The site is under heavy usage, but just wanted to know if there is some kind of “estimations” for a correlation Users/VolumeOfTraffic - Memory.

I saw that a “Swap” was recommended, pardon my ignorance, but how do you achieve that, it’s recommended? Or is like removing the incorporated Rate Limiter (which was not recommended by Sam)

I’m running the latest version of Discourse.

---

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