# Discourse Docker HW reserved/used (CPU, RAM, Disk) and how to manage it

**URL:** <https://meta.discourse.org/t/discourse-docker-hw-reserved-used-cpu-ram-disk-and-how-to-manage-it/265010>\
**Category:** Self-hosting\
**Tags:** server-resources\
**Created:** [May 15, 2023, 8:11am UTC](https://meta.discourse.org/t/discourse-docker-hw-reserved-used-cpu-ram-disk-and-how-to-manage-it/265010 "2023-05-15T08:11:39Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Crius](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/crius/32/317214_2.png) [@Crius](https://meta.discourse.org/u/Crius)\
**Post date:** [May 16, 2023, 8:34am UTC](https://meta.discourse.org/t/discourse-docker-hw-reserved-used-cpu-ram-disk-and-how-to-manage-it/265010/4 "2023-05-16T08:34:06Z")

</div>

Gotcha, with a lot of RAM I had read around not to worry too much about SWAP so I created 8GB just to not be totally out of a “safety net” if that makes sense.

Can you elaborate a bit further about what I should worry about in terms of swap activity?

Anything related to SWAP I could find in the dashboard is this:

 ![image](https://global.discourse-cdn.com/meta/original/4X/9/6/0/9609efdcf073aa1a55e710b0b917062a8dfe855c.png)

And this is the full memory stack:

 ![image](https://global.discourse-cdn.com/meta/original/4X/b/9/8/b9866b03d88b00dba1c4aca73485cbb6a1e7325b.png)

I’m used to work with containers/k8s for work so this details on a VM level eludes me in terms of what I’m supposed to keep an eye on.

If you have some entry level links and don’t want / don’t have time to write an essay here, it’s still appreciated 🙂

---

_[View the full topic](https://meta.discourse.org/t/discourse-docker-hw-reserved-used-cpu-ram-disk-and-how-to-manage-it/265010)._