This repository has been archived by the owner on Nov 30, 2021. It is now read-only.
chore(contrib/vagrant): lower memory to 2GB #744
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
When we had the full stack on one VM, 4GB was reasonable. Now that we are launching multiple VMs and splitting the stack across them, each one should use less memory.
|
LGTM. Note that we are (intentionally) using 4GB in the single-machine developer Vagrantfile in the project root. |
|
Yup, that should still have more memory since it's using a larger stack. |
|
I'm holding off on this one. We should understand how much memory our stack currently uses up on one node, divide that by 2 (7 components on 3 nodes rounded down to an even number), then add ~1GB of memory for user apps. That's how much memory we should have on each node. If the builder or the controller takes up a lot of RAM (which I doubt), then we should probably keep it as-is. |
|
Oh wait, never mind. 12GB of RAM just to get a vagrant cluster up and running? Eww. LGTM. |
bacongobbler
pushed a commit
that referenced
this pull request
Apr 16, 2014
chore(contrib/vagrant): lower memory to 2GB
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
When we had the full stack on one VM, 4GB was reasonable. Now
that we are launching multiple VMs and splitting the stack
across them, each one should use less memory.