Dynamic Memory Assignment #30
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…he container. It uses the introduce new variable MEMORY_LIMIT that wasn't in use at the moment, using the following approach.
- We get the amount of memory reserved for the container and substract a little bit for the rest of the container and everyhing else is set as Xmx. We have two way to set the amount of memory that is going to use for the system (not BW) based on variables:
- MEMORY_FIXED_LIMIT (in MB): in case you want to substract a fixed amount of memory like 128 or similar.
- MEMORY_DYAMIC_LIMIT in (percentage from 0-100): in case you want to substract a percentage of the assigned memory.
In both cases if the memory that is dedicated is less than 128 M it is ignored and use a failsafe memory (memory assigned - 128). IN case only MEMORY_LIMIT is set, do same thing (memory assigned - 128)
Also added a DEBUG trace that shows the amount of memory that is going to be assigned:
|
Related to #29 |
…ess level flowlimit with the following syntax "version.componentName:value1;version.componentName2:value2;" to be able to specify flowlimit at the component level.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Included the option to set the Xmx based on the configured memory to the container. It uses the introduce new variable MEMORY_LIMIT that wasn't in use at the moment, using the following approach.
In both cases if the memory that is dedicated is less than 128 M it is ignored and use a failsafe memory (memory assigned - 128). IN case only MEMORY_LIMIT is set, do same thing (memory assigned - 128)
Also added a DEBUG trace that shows the amount of memory that is going to be assigned: