-
@nebulon At times I see that the Cloudron is not responsive (browser timeouts, which could be something other than a busy Cloudron server). I am also having an issue when using external monitors to check the health of my Cloudron (Uptime Robot, BetterStack). Attempts to use the API health check to return Cloudron version sometimes fails (causing Uptime or BetterStack to issue an alert). The same problem happens using the appid API call to check my Kuma instance. Again, I am not sure why this is happening or if it relates to the swapfile and performance. The GET failures are intermittent, but frequent enough to cause me to disable these alerts.
Given the CPU/RAM/Disk of this server, I would not expect any of this to be an issue. I am not seeing anything in the box log that might suggest a problem. An article I was reading prompted me to look at the swapfile and utilization. Inside Cloudron, the monitoring chart seems to show a 50/50 split between RAM and swapfile. Ideally, Cloudron would use close to 100% RAM, but if subsystems dictate a 50/50 split, then perhaps I should increase from an 8GB swapfile to something much larger (I have enough disk to accommodate this easily).
Theoretically, suppose I allocate 1GB to /apps.swap? How would that impact Cloudron performance? Would applications crash? Wait for available swapfile RAM? Just trying to figure out how to best allocate extra resources to get better performance.
-
J james marked this topic as a regular topic on
-
J james moved this topic from Support on
-
I think we would have to separate some issues here. Cloudron's main service (box process) is not setting up anything special regarding swap, so since you say you get response issues on the Cloudron API itself and system RAM is not the issue here from your perspective, I guess something else is at play causing this. So maybe before going into apps, first try to figure out what is happening on those API calls.
For a start check the
/home/yellowtent/platformdata/logs/box.logduring the time when the API calls fail. This should show some error to work with.If this is some virtual server, it could also mean that CPU or disk becomes very slow if you share the same hardware resources with other virtual servers. Such usage is usually not visible in your system stats but can have a real impact.
Also keep
vmstat 1via SSH running for some time and look at thesi(swap in) andso(swap out) numbers, to get a sense of how the system is loading and offloading memory pages live. -
@nebulon Great point about the VPS. I am going to try "monitoring" two different Cloudrons at different VPS providers. Let's see if there is a similar pattern (perhaps something related to Clourdon) or if one Cloudron is having API issues, then that would suggest a VPS provider issue. In any case and on all Cloudrons, I will check the box.log to see if there is something happening on the Cloudron when API issues appear.
Independent of the API/heartbeat issues, what is your recommendation on managing the swap file and it's size?
-
The rough rule here would be, that if the server has limited RAM, then use a larger swap file. If you have plenty of RAM a smaller say 4GB swap for edge cases to increase stability is good.
What limited RAM means kinda depends on how much apps and which apps you have installed. So this is really hard to say.
Overall unless you are sure the swapping is the actual bottleneck, I would not dive too much into that and first check other things.
-
@jdaviescoates All good, clearly it can't be more specific ;-]
Banhammer time
-
Hello @sponch
It depends on your provider how he initializes the Ubuntu system.
A good guide is https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/8/html/managing_storage_devices/getting-started-with-swap_managing-storage-devices#recommended-system-swap-space_getting-started-with-swap
According to the Red Hat guide, 4GB SWAP for a 32GB RAM system is the minimal recommended.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login