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.
This patch solves #755:
add a new set of configuration to be able to configure memory constraints based on a percentage of maximum memory and not an absolute number: server.memory.data.percentage, server.memory.index.percentage server.memory.pk.percentage. Actually data and pk are simply a configurable value for a previous fixed one. The index is new, see below
add a new set of configuration to enable indexes / data pages memory separation. Up untill now data and indexes was stored in the same memory space with the same constraint. Now you can configure server.memory.index.percentage (maximum memory percentage value, defaults to 0%) or server.memory.index.limit (byte fixed value, default to 0). If dedicated index memory resolves to a value more than 0 it will be used instead of data memory. By default index will continue to share data memory
Due to memory inspections I noted that memory occupancy is evaluated enough well, we don't need to keep up to 50% memory free by default for "every else". Increased data default space from 30% to 50%.
[ x ] I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004