brozek/website
1
0
Fork 0
mirror of https://github.com/Brandon-Rozek/website.git synced 2024-09-19 06:05:14 -04:00
Code Issues Projects Releases Packages Wiki Activity

Added warning

Browse source
This commit is contained in:
Brandon Rozek 2024-06-16 18:04:13 -07:00
parent 0baa5cb236
commit 0e72302e88
No known key found for this signature in database
GPG key ID: 26E457DA82C9F480
1 changed files with 2 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
content/blog/managing-mongodb-resource-usage-docker-compose.md
View file

@ -8,6 +8,8 @@ math: false
medium_enabled: false medium_enabled: false
--- ---
*Warning: This technique does not work for the older Docker Compose v3*
One of my web services utilizes MongoDB as the database backend. It lives on one of the smaller sized virtual private servers with only 1GB of RAM and 1 CPU. Every so often I encounter a scenario where MongoDB is taking all of the sytem resources, so I started looking into how to limit it. One of my web services utilizes MongoDB as the database backend. It lives on one of the smaller sized virtual private servers with only 1GB of RAM and 1 CPU. Every so often I encounter a scenario where MongoDB is taking all of the sytem resources, so I started looking into how to limit it.
First, we can set some limits to container in general within docker-compose. First, we can set some limits to container in general within docker-compose.