|
General Asylum General audio topics that don't fit into specific categories. |
|
|
|
General Asylum General audio topics that don't fit into specific categories. |
|
In Reply to: It is you who is confusing posted by E-Stat on November 23, 2024 at 12:44:47:
You just told me in your previous post how simple it was that your VM image is loading completely into RAM and mine is not because I don't have enough RAM. With that in mind how tiny is your VM image that it loads entirely into RAM?If that's your understanding then it's not complicated at all - but that's not how it works as I have already explained.
Now you weave and say....
"I give Win10 8 GB of memory and it gets all of it when booted."
Hmm, I give Windows 10 6 GB of memory yet my Windows 10 memory foot print is only 2GB. Is that because I have 'only' 16GB of RAM? ;-)
Ok then.
[Edit]: Just for grins I down configured my Win10 VM memory to 4GB of RAM (1/4 of my physical 16GB just like your 8GB is 1/4 of your 32GB physical). Yet according to Activity Monitor my Win10 execution memory footprint is still just around 2GB. By your logic mine should have went up to 4GB. I certainly have enough RAM. Me thinks something is wrong with your logic or possibly your VM configuration... or maybe you're not using Activity Monitor correctly. Maybe you have a memory leak from an App within your VM that is not releasing memory and that might be why you are pegged with a 8GB memory footprint for your Win10 VM. I dunno.
But it's not as simple as you think it is.
Edits: 11/23/24
This post is made possible by the generous support of people like you and our sponsors:
Follow Ups
- I'm done going in circles with you - AbeCollins 13:02:30 11/23/24 (3)
- RE: I'm done going in circles with you - E-Stat 13:59:13 11/23/24 (2)
- You simply don't get it and never will - AbeCollins 06:41:48 11/24/24 (1)
- Have a good day! - E-Stat 06:58:11 11/24/24 (0)
Top of Page ]
[ Contact Us ]
[ Support/Wish List ]
[ Copyright © 2025, Audio Asylum, all rights reserved ]
