-
Notifications
You must be signed in to change notification settings - Fork 0
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
[Feature]: configure max amount of used memory #316
Labels
Env: Documentation
requires an update of the documentation
L: ★☆☆
Expect low difficulty
New feature / Improvement
new features and improvements of existing features
Topic: Usability
changes to improve the usability of the program
Milestone
Comments
kitsudaiki
added a commit
that referenced
this issue
Jul 14, 2024
Added config-entry to define the persentage of max amound of used free memory. Also added the option to the example-config, helm-chart and ansible-playbook. Default is 0.5 or 50%.
kitsudaiki
added a commit
that referenced
this issue
Jul 14, 2024
Added config-entry to define the percentage of max amount of used free memory. Also added the option to the example-config, helm-chart and ansible-playbook. Default is 0.5 or 50%.
Added new config-group and -entry:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Env: Documentation
requires an update of the documentation
L: ★☆☆
Expect low difficulty
New feature / Improvement
new features and improvements of existing features
Topic: Usability
changes to improve the usability of the program
Feature
Description
At the moment the maximum amount of used memory is hard-coded to 80% of the current free memory. This can result in bad results, if you forget to stop the program and do some other tasks on the same system, which your memory is nearly full...
To prevent this in a dev-envirionment, a config-entry should be added to make it configurable, how much free memory should be used by Hanami for pre-allocation.
Acceptance Criteria
Additional Information
Blocked by
How to test
The text was updated successfully, but these errors were encountered: