Cloudron Forum

I get this: docker inspect 5130e1789e1e | grep Memory "Memory": 5368709120, "MemoryReservation": 0, "MemorySwap": -1, "MemorySwappiness": null,

@james for sure: Hetzner vServer CPU4 Core "AMD EPYC-Milan Processor" Memory16.37 GB RAM & 4.29 GB Swap Cloudron v8.3.2 on Ubuntu 22.04.5 LTS Allocated Ram: 4GB Websites monitored: 150 each 12 hours

@visamp said in New Hetzner Server Installation Best Practices: Do you recommend installing CrowdSec or not? Maybe it's overkill? I had it installed once, looked at pretty graphs for maybe 4–5 days. Then I forgot it, re-setup the server and did not install it again. So, I can not even tell you if it was helpful or not. But what I can say is, no one here really uses crowdsec, nor maintains support for it with cloudron. Good thing is, backup or snapshot, try it, decide for yourself, rollback if it is not to your liking.

Thx, I´ve look into that, it looks like the same!

Ah yeah, that's what I thought. Moved the build app to somewhere else. Would be nice to add --cpu-quota to the build command to mirror the apps settings (from https://dev.to/code42cate/dont-build-docker-apps-without-this-flag-48kg)

@ekevu123 Previously, we used something called "CPU Shares" (--cpu-shares in docker) . This option was a bit hard to understand since it comes to picture only when there is CPU contention between various apps (i.e when a server is overloaded to start with). We removed this and replaced it with an easier to explain "CPU Limit" (--cpu-quota in docker). This corresponds to how many cycles your app should be given. Like, you can say, give only 2 cores max to this app (in any situation). By default, apps have access to all your CPUs. However, isn't the point that the default should be less than that so that one app cannot take down the whole server? We couldn't think of a good default. Otherwise, apps will start out "crippled" and we thought it's better this way. I think if you have apps that are causing problems, only then should you look into tweaking this. This would be a stop gap measure before you try to report the issue and get the app fixed...

@SansGuidon you are absolutely welcome

@pauljacobson ah yes, the fix for haraka is coming. I recently submitted a patch upstream for this which has now been merged - https://github.com/haraka/Haraka/pull/3104 .

@DualOSWinWiz the warning is like a softlimit warning. Basically the system will calculate the rough estimate of memory requirement based on the already installed apps and checks with the available memory of the whole system. Since memory usage heavily depends on the use-case and usage (number of concurent users for example) of apps on a Cloudron, we warn upfront to warn the admin, to at least keep an eye on the system to not overload it.

I don't really know what the calendar-resource Nextcloud plugin does, but it seems after installation, you may have to use the occ tool. This is described at https://docs.cloudron.io/apps/nextcloud/#running-occ-tool

I think there was a task to integrate better with prometheus or grafana but it got lost. Let me check if we want to do this for 7.2

@timconsidine Thanks, that is good to hear. I think it is quite natural when somebody discovers Cloudron to go wild installing things to try them and that takes quite a lot of RAM. One other benefit of smaller applications is that there are often fewer lines where bad code could hide or where things could go wrong.

Here we go : https://docs.cloudron.io/apps/#low-resource-warning