Skip to content

Resource Limits

XternA edited this page Apr 10, 2024 · 6 revisions

By default, the tool applies the LOW profile resource limit.

The limits will vary based on each system as it is dynamically calculated based on the system's hardware.

Pick a new resource limit utilization based on current hardware limits.

Limit Type Applied:       MIN
Number of CPU Cores:      4
Total RAM:                23981 MB
Calculated CPU Limit:     0.5
Calculated RAM Limit:     2997 MB
Calculated Reservation:   1498 MB

1. BASE   -->   320MB RAM
2. MIN    -->   12.5% Total RAM
3. LOW    -->   18.75% Total RAM
4. MID    -->   25% Total RAM
5. MAX    -->   50% Total RAM
0. Return to Main Menu

Select an option (1-5):

The goal is to use as little resources as possible and these applications generally don't take up too much resources. However, do keep in mind that since it's running a stack with multiple applications then of course the overall resource will be much higher than only one or two applications alone.

For a safe setting, LOW profile is used to ensure that weak hardware resources are set with a limit not too low. The recommendation is to start here and slowly dial the resource down to MIN or BASE eventually. Though in typical use cases MIN and BASE work fine without issue on a Raspberry Pi 4 (4GB RAM) for instance.

For systems with plenty of RAM, you can go to a higher setting if you want to let the application use as many resources as possible without being killed and restarted due to resource limits. It's just an option available here.

The limits set are preserved until the settings are reset back to default or the configuration file is deleted.

You can also check the resource used by the stack in docker with docker stats.

Resource Limit Error

Refer to Enabling CGroups section if there are issues with the resource limits not applying.

Clone this wiki locally