Quote:
Originally Posted by gguruusa
You are reading incorrectly.
First, unlike regular loading, xip modules have larger boundaries. Loading a code section that barely fills a region is very wasteful.
2nd, "Freeing more ram" is a misleading synopsis. What you are doing is consuming less RAM than you would if multiple programs needed the code section. You are consuming more memory than if no program needed the module.
3rd, scarce resources can be an issue when consumed by never-unloaded xip modules.
The moral: don't convert everything to xip. Candidates for conversion are things which are a) used frequently b) used by multiple programs and c) have code sections just under the boundary size.
|
Yes, I understand I run the risk of killing my VM after some further reading. Is that what you are referring to?
Also, point 2 is WELL received. I noticed LESS ram after a clean boot. But loading programs that I XIP'd consume less now when running (see my iGO victory which is my main concern here. I use it alot and have to FREQUENTLY reboot to free up enough RAM. The executable is 5MB which is 25% of my free RAM alone. I know, it's probably an awfully large exe to be converting to a module, but what's the worst that can happen? A recook? Just another reason to do so....)