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

<div class="post-metadata">

**Author:** ![Ed\_S](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ed_s/32/134015_2.png) [@Ed\_S](https://meta.discourse.org/u/Ed_S)\
**Post date:** [May 15, 2023, 1:13pm UTC](https://meta.discourse.org/t/discourse-docker-hw-reserved-used-cpu-ram-disk-and-how-to-manage-it/265010/3 "2023-05-15T13:13:46Z")

</div>

Briefly, I would say

- don’t worry about CPU usage unless it’s saturating all cores.
- don’t worry about RAM usage, worry instead about swap activity.
- probably start a new thread about DB size growing 10x

If your system offers swap activity metrics, use them. If it doesn’t, look for disk activity on the device holding the swap space.

---

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