-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
set memory limits for all services #460
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
feature-flag-service limit of 160M is too strict and causes the container to be Killed in my docker compose deploy. It may be environment specific, but a minimum limit I can get this working is 1600M. |
@styblope 1600M is definitely not normal. Which OS is this on? |
I know, it's weird, but I stepped up piece by piece until the container stopped getting killed. It's on x86_64 Fedora 34 VM (vsphere), 8GB RAM, Docker CE 20.10.17. Maybe it's a docker thing? Or a startup ram hike. |
* set limits for all services * memory limit for services * re-add quoteservice to frontend dependency * Update docker-compose.yml Co-authored-by: Austin Parker <[email protected]>
Changes
Sets reasonable memory limits for all services, based on an 80% memory target for each service, running the app for 7 days (minimum of 20M).
Data used by this PR incorporated the memory limits shown in the chart above which is a 7-day run on EKS. Some exceptions for loadgenerator, email, and quote services where I used data from docker stats after running the app on my local machine for several days.
CHANGELOG.md
updated for non-trivial changes