 
|
Audio Asylum Thread Printer Get a view of an entire thread on one page |
For Sale Ads |
|
|
Audio Asylum Thread Printer Get a view of an entire thread on one page |
For Sale Ads |
73.229.163.4
In Reply to: RE: Three deletes? posted by E-Stat on November 23, 2024 at 11:33:33
"MacOS locks down exactly what it needs - if you have available resources!"
Sure but you're saying that your Win10 8GB VM needs the full 8GB out of 8GB of RAM allocated to it (100%)? I find that curious because my 6GB Win10 VM is taking only 2GB of RAM out of 6GB (33%) made available to it..... and I have the resources for it to take more if needed.
Applications like Parallels CAN lock-down more than you need if you configure it to do so. I let the automation within Parallels dynamically adjust if needed.
Follow Ups:
that is the size of the (memory) image! Not a complicated topic.If I had less memory, mine would do a partial load like yours.
Edits: 11/23/24
"Because that is the size of the image! Not a complicated topic."Nope. Key concept: VM image size does not equate to execution memory footprint. The VM image does not consume RAM that equates to the size of the VM image. If that were true my 74GB image would try to use 74GB of RAM. So me thinks you're confused.
The image size is the size of the VM file which contains the OS and every App that you have installed in that VM. The image resides on disk. My Win10 VM image is 74GB on disk yet Windows10 is consuming only 2GB of RAM while executing (running). Hmm?
In any case it's working for you so you don't have to understand it.
My Windows 10 VM Image
Edits: 11/23/24 11/23/24
the entire Windows volume size with allocated memory. They are not the same. I give Win10 8 GB of memory and it gets all of it when booted.
Because I have enough system memory to do so. You don't.
This really isn't a complicated topic.
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
With that in mind how tiny is your VM image that it loads entirely into RAM?Let's back up several posts where that question has already been answered. And consider that what loads into memory is not the entire disk! It's the fixed allocation of space for Windows applications to use. Mine has two CPUs allocated. All I use presently is Quicken for older financial records.
Is that because I have 'only' 16GB of RAM?
I think you're finally getting it!
Yet according to Activity Monitor my Win10 execution memory footprint is still just around 2GB.
That's all MacOS has available.
But it's not as simple as you think it is.
Sure it is. MacOS uses what's available. I have plenty of memory so there is no need to short it. All 8 GB can be accessed by Win apps immediately w/o swapping in that world!
Get 32 GB and yours would do the same. LOL!
Edits: 11/23/24 11/23/24
Your concept of how macOS & Parallels "allocates" memory for your Win10 VM is completely incorrect as I have tried to explain even with examples. But you still don't get it (or refuse to get it).
First I had to correct you on what a "VM image" is and how it does not fully load into memory. You back tracked on that one after I showed you that my VM was 74GB in size. Only then did you start to get the concept of the VM "image". And then I offered up the concept of "memory footprint".
You'll never get it because you insist that you are correct and want to save face. I've seen it in every one of your arguments here in the asylum and not just with me.
But it's not my place to educate you and I really don't care if you continue to live in your fantasy world of how things work.
I'm simply observing reality. Accept or ignore as you will. :)
| FAQ |
Post a Message! |
Forgot Password? |
|
||||||||||||||
|
||||||||||||||
This post is made possible by the generous support of people like you and our sponsors:
Top of Page ]
[ Contact Us ]
[ Support/Wish List ]
[ Copyright © 2024, Audio Asylum, all rights reserved ]
