Limit docker container RAM usage
With the release of Helmut 4.8.x and the corresponding update to the Java environment, it is now possible to limit the maximum amount of RAM a container can allocate.
New Helmut4 Installation
By default, this RAM limitation setting is included in every new Helmut4 installation, whether it is a single server or a cluster. This setting is now a default parameter in the stack YAML file.
Updating Existing Helmut4 Installations
Existing Helmut4 installations can be updated to use the same resource allocation settings. To implement this change, users need to update the stack YAML configuration.
You can download the default stack YAML file from our repository for reference:
Single Server: https://repo.moovit24.de/install/config/docker-compose.yml
Cluster System: https://repo.moovit24.de/install/config/docker-compose-swarm.yml
Please note that you may need to adjust these values to meet your system's requirements.
For example, a system with high I/O and CPU demands might require increased memory for linked containers such as io, co and mongodb.
Example
Here is an example screenshot of the language container:
Default RAM limits
The following values can be considered as defaults:
Container / Image | Memory (MB) |
---|---|
traefik | 250 |
hp | 100 |
hw | 100 |
fx | 1500 |
io | 2000 |
co | 2000 |
hk | 1500 |
users | 1500 |
streams | 2000 |
preferences | 500 |
metadata | 250 |
logging | 250 |
amqp | 250 |
license | 250 |
language | 250 |
cronjob | 250 |
mongodb / mongodbrs | 2000 |
mongodb_backup | 250 |
mongodb_admin | 250 |
rabbitmq | 2000 |
hc | 2500 |
Last updated