Install the app
How to install the app on iOS
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Active RAM remains high when exit Parallels with XP Suspense
- Thread starter hln98
- Start date
unused_user_name
Pro
This is not a bug.
There are lots of different kind of memory in OSX. "Free" means that the OS is not using it to cache anything. The "Free" memory should always be 0 if the system is going to have optomal performance, as it uses RAM as a cache to speed things up.
What you want to look at is "Inactive" memory. That is memory that is being used as a cache but it not assigned to any program. MacOS will not dump memory immeadiately. Try an experament. Cold reboot your mac and start Parallels. Time (with a stopwatch) how long it takes to go from the click that start Parallels until your VM is ready to go. Now exit Parallels. Without doing anything else first, restart Parallels.
It should be much faster the second time because MacOS does not clear out the RAM. It just marks it as being unused so that other programs can use it if needed. This is a rather old optimization as virtual memory advancements go. Windows Vista and MacOS uses it, and a bunch of research OSs from the 80's (and maybe solaris?) also uses this technique. Windows XP does not do this, which is why you perhaps are not used to it.
There are lots of different kind of memory in OSX. "Free" means that the OS is not using it to cache anything. The "Free" memory should always be 0 if the system is going to have optomal performance, as it uses RAM as a cache to speed things up.
What you want to look at is "Inactive" memory. That is memory that is being used as a cache but it not assigned to any program. MacOS will not dump memory immeadiately. Try an experament. Cold reboot your mac and start Parallels. Time (with a stopwatch) how long it takes to go from the click that start Parallels until your VM is ready to go. Now exit Parallels. Without doing anything else first, restart Parallels.
It should be much faster the second time because MacOS does not clear out the RAM. It just marks it as being unused so that other programs can use it if needed. This is a rather old optimization as virtual memory advancements go. Windows Vista and MacOS uses it, and a bunch of research OSs from the 80's (and maybe solaris?) also uses this technique. Windows XP does not do this, which is why you perhaps are not used to it.
neosublime
Member
I am seeing this too. It shows my "Active" RAM as half used after I exit Parallels. I startup my Mac, check my RAM. Lauch Parallels only. Let it run for a bit, then suspend it. Wait a bit and recheck my activity monitor, and my "Active RAM is still high, but no paticular app is using alot of RAM. When I suspend it actually increases the "Active" RAM.
MBP CD 2.0, 2GB, WinXP Pro SP2, 256MB
MBP CD 2.0, 2GB, WinXP Pro SP2, 256MB
neosublime
Member
Temp fix, disable suspend, and switch to power off VM. Reclaims RAM.
This is indeed a bug. The original poster and I were referring to the active memory, not free or inactive memory. When an application quits, the memory that it uses should become inactive or free. In this case, Parallels sometimes does not allow the kernel to release the memory, and it stays active indefinitely. That memory will never be reclaimed by another process until the computer is restarted. Again, this behavior will only present itself when the VM is suspended. If you stop the VM and then quit Parallels, the memory that Parallels was using becomes inactive.