-
Notifications
You must be signed in to change notification settings - Fork 240
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disable dynamic memory assignment on Windows #607
Comments
We left dynamic memory assignment as we see no problem with the behaviour for the average user. Wh n more resources are needed, they are assigned without need to interfere . However, do you think this should be disabled? |
Thanks for the response @gbraad.
I'm not sure if I fit the "average user" category 😄. It was my first usage of Hyper-V & crc. It didn't take long once my machine slowed to look the resource usage and track down the Dynamic memory assignment area.
No. In theory it makes sense. While I was able to quickly figure things out, my user experience was thrown off a bit with the CRC config being set to 8GB however the dynamic Max was set well above that. |
for me it usually starts to settle at about 11 or 12GB (the machine has 32GB available). I have to admit, this is a lot, but with fixed memory we end up having other issues. The ideal would be to put OpenShift 4.x on a diet, but these are on-going discussions ... There is another issue that discusses them, just at the moment unable to track it down. |
One might argue about whether dynamic memory should be the default or not, but once I've told crc to use a certain amount, I would not expect it to use more. To quote the
Currently, this help text is not correct, since the default is not 8192MiB, but "dynamic, max 1TB". |
I'm using it with my CRC VM. Let see if this is working well |
the problem is partially due to how OpenShift/K8s aggressively deals with memory use. All my VMs run on a 24GB T460p work laptop (fedora, rhel and CRC) at the same time. All enabled with dynamic memory. Want more feedback about this... before disabling. I could consider adding a default max memory option... as this would not remove the current behaviour, but restrict it ? For example: PS> Set-VMMMemory crc -MaximumBytes 12GB to restruct to a mamximum of 12GB |
Docker Desktop is not using Dynamic Memory !. I will report if I found any issue with my CRC after a while. |
@gbraad I have restricted the memory on my crc VM to a reasonable size and that works well. However, I still think the default is wrong: hogging most of my machine's memory when I tell the CLI explicitly how much memory I'd like it to take is unfriendly, IMO. I think I am a pretty good stand-in for your user community and I would not have expected that at all. |
If this gets changed a new documentation entry is needed to deal with this
as previously, Windows users did not need to change the memory usage. The
current suggestion for the hypervisors is to do `crc delete, crc start` to
handle this (as it works across all hypervisors. or a platform specific
entry is needed to handle this @kowen WDYT? I guess this should be added
as an entry to the Release Notes and perhaps a topic to deal with this ?
As currenrtly, users that develop a large application did not have to modify
the default value when starting CRC as the memory usage scaled on
demand. Troubleshooting? For consistency it is best to 'fix' this.
Note: it is not about changing this to fixed memory, but changing the
default behaviour.
|
Thank you for the local 4.x OpenShift environment. I've been using it over the past couple days to review Tekton/Openshift Pipelines and its working great! One small thing I've uncovered that I thought I'd surface.
General information
CRC version
CRC status
CRC config
Host Operating System
Steps to reproduce
Starting OpenShift cluster ... [waiting 3m]
. The memory usage of the VM will continue to creep higher until the machine is unusable.Expected
Would expect the Hyper-V VM to be limited to 8GB of RAM.
Actual
It looks as if on my machine the Dynamic Memory section of the crc image was turned on and the Maximum RAM setting was established at 1TB. This was well over what I have installed on my machine (16GB).
I'm unsure why the memory was creeping higher and higher. Once I spotted the max memory setting and lowered it to 8GB everything has been running great.
The text was updated successfully, but these errors were encountered: