Running Cloudron on eMMC – How to Reduce Writes?
-
Hi there!
I decided to install Cloudron on my home mini PC, using the built-in eMMC storage for Ubuntu (to keep my M.2 drives free from the OS). I understand that to preserve the longevity of the eMMC memory, it's important to reduce write operations as much as possible. There are plenty of suggestions online — disabling swap, lowering the swappiness value, tweaking or disabling system logging, etc.
But my main question is: how can I minimize Cloudron's impact on system disk wear?
I realize it would be much easier to just dedicate one of the M.2 SSDs for the OS and Cloudron, but at this point, it’s become more of a curiosity project
-
It is a bit to tinker, but you can see all locations Cloudron mostly writes to at https://docs.cloudron.io/storage/#default-data-directory and you could relocate those to the M.2 drive then (see relocate section in the docs page)
Further for swap you may also just add the swapfile onto the M.2 drive.
-
It is a bit to tinker, but you can see all locations Cloudron mostly writes to at https://docs.cloudron.io/storage/#default-data-directory and you could relocate those to the M.2 drive then (see relocate section in the docs page)
Further for swap you may also just add the swapfile onto the M.2 drive.
@nebulon said in Running Cloudron on eMMC – How to Reduce Writes?:
see relocate section in the docs page
Thank you! I managed to move everything except the swap. I'm still not entirely sure about the correct steps for that. As for the Docker images — I haven’t moved them yet, since they don’t take up enough space to be a problem at this point.
-
Great. For swap you can follow the docs at https://docs.cloudron.io/storage/#swap just make sure the swapfile is located within the other disk.
@nebulon said in Running Cloudron on eMMC – How to Reduce Writes?:
make sure the swapfile is located within the other disk
Great, everything’s working now. Thanks again!
