One Use That May Make Sense
I can think of no good reason to keep any of these apps running on your system all the time. In all my tests, at best they took more than they gave; at worse they made my systems slower and less stable.
But I can think of one instance where it might be useful to have a memory optimizer on hand for occasional manual use: It's benefit #1 mentioned above -- the ability to recover memory orphaned after an applications crash.
The freeware RAMpage memory optimizer, RAMpage, for example, has a command-line-driven "run once then exit" mode. I've coded the command-line parameters into a batch file, and I now run RAMpage after some other application crashes: RAMpage loads, opens up a hole in RAM, tries to recover "orphaned" memory left by the crashed app, defrags what's left, and then exits. I'd never leave RAMpage (or any memory optimizer) running all the time due to the problems listed above, and because of the relative rarity of applications crashes. But as a simple, free way to try to clean up after an app does crash (and thus possibly avoiding the need to reboot) it seems to work pretty well.
In fact, after some tinkering, I've developed a four-part strategy that gives me great results: I'm able to prevent most memory- and resource-related crashes in the first place, and can skate into the single digit range of User or GDI resources without any trouble at all. And when an app does die for some reason, I can now recover orphaned general memory without rebooting, using RAMpage. In my tests, I've gone day after day after day with my resources rock-steady and stable.
The strategy involves several approaches, including optimizing all Windows memory areas -- the swapfile, Vcache, and so on. I'm putting the final touches on the four-part plan now, and will present it in detail in the next installment of this series. Stay tuned! - http://www.informationweek.com/story...7200583&pgno=5