Increase PG Pod resource requirements #188
Merged
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
- Provide reasonable minimum default resource requests for a PG/MIQ deployment on OpenShift - Increased shared_buffers to 1GB - Increased minimum RAM resource request to 4GB - References : https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server https://access.redhat.com/documentation/en-us/red_hat_cloudforms/4.5/html/deployment_planning_guide/introduction#virtual-hardware-requirements
carbonin
approved these changes
Jul 26, 2017
templates/miq-template.yaml
Outdated
| @@ -841,7 +841,7 @@ parameters: | |||
| displayName: PostgreSQL Min RAM Requested | |||
| required: true | |||
| description: Minimum amount of memory the PostgreSQL container will need. | |||
| value: 1024Mi | |||
| value: 4096Mi | |||
templates/miq-template.yaml
Outdated
| @@ -784,7 +784,7 @@ parameters: | |||
| - name: POSTGRESQL_SHARED_BUFFERS | |||
| displayName: PostgreSQL Shared Buffer Amount | |||
| description: Amount of memory dedicated for PostgreSQL shared memory buffers. | |||
| value: 256MB | |||
| value: 1024MB | |||
|
I'm okay with this. For development I'm already clearing out all the requests and limits and letting my minishift VM swap. |
|
Checked commits fbladilo/manageiq-pods@18130ea~...2841b6f with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0 |
|
Adjusted size suffixes to Gigs... |
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.
@carbonin @bdunne Follow up on this one...
https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server
https://access.redhat.com/documentation/en-us/red_hat_cloudforms/4.5/html/deployment_planning_guide/introduction#virtual-hardware-requirements
The kubernetes scheduler will only attempt a pod placement on a node that satisfies the minimum request, the shared buffer calculation is taken from the PG tuning guide at 1/4 of the available RAM. In this case, we calculate from the minimum memory request (guaranteed) and not the max memory limit set by default at 8GB and enforced via cgroups.