Draft
Conversation
Since we moved to minikube on macOS we increased vm memory by 2 GiB.
This creates too much memory pressure on developer machine, running many
memory hungry applications (Chrome, Cursor, VScode, Slack, Teams). Lets
give them back 3 GiB. The clusters should work fine with 1 GiB extra
memory.
Available memory in managed cluster:
$ free -h
total used free shared buff/cache available
Mem: 6.8Gi 5.5Gi 151Mi 1.0Gi 2.3Gi 1.2Gi
Swap: 0B 0B 0B
Available memory in the hub:
$ free -h
total used free shared buff/cache available
Mem: 4.8Gi 4.1Gi 195Mi 947Mi 1.6Gi 676Mi
Swap: 0B 0B 0B
Signed-off-by: Nir Soffer <nsoffer@redhat.com>
nirs
force-pushed
the
minimize-vm-memory
branch
from
371f6e4 to
02fc9ff
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Since we moved to minikube on macOS we increased vm memory by 2 GiB. This creates too much memory pressure on developer machine, running many memory hungry applications (Chrome, Cursor, VScode, Slack, Teams). Lets give them back 3 GiB. The clusters should work fine with 1 GiB extra memory.
Testing
Issues
Tested in CI in this PR and in #2408 - we had 2 CI failures in the e2e run out of 4. Unlikely to be random failure.
Failed runs:
Successful runs: