|
01/05/2005, 10:17 AM
#10
I think part of the confusion when we talk about "memory issues" is that there are really two different memory changes on the Treo 650.
First, the NVRAM issue that affects the amount of *storage* space. This has been reduced due to the bookkeeping overhead, true, and that's what a lot of people notice immediately -- they can store fewer apps in the device. This is where ZLauncher and similar utilities can help, by managing the offloading of storage onto the SD card.
But I'm seeing another, more troublesome problem with the whole way the memory was redesigned to *run* applications.
Now that the Palm has the notion of separate storage space and RAM for execution, it seems to me that they didn't leave enough room to really run applications the way we're all used to doing it. Now that apps have to be copied from storage to RAM, and then executed, this new area is filling up.
Some people won't see this, as they tend not to run apps that take a ton of runnable space, mostly storage space. But I'll wager anyone running GoodLink (which takes up, I'm guessing, a lot of the RAM) will see this almost immediately, as I did.
Again, it's not a lack of *storage* space -- I've managed it so I have about 6 megs free of storage. It's lack of RAM space for the apps I want to run.
Worse yet, there's no way to monitor how much of this space is available, nor any way to really manage the memory.
Finally, I personally believe there is a memory leak in there somewhere. It feels to me like apps are running and then failing to release memory they've allocated. This could be what Palm means when they say that some apps won't "like" the new NVRAM file system... or it could be a problem somewhere in the new scheme on the device.
Bottom line, I really, really hope PalmOne addresses BOTH issues when they issue the memory patch. They need to reduce the overhead that is incurred when storing files internally, which will help. But the killer fix will be increasing the amount of RAM available to running apps, or at least implementing a system that allows you to page in storage from other sources (like the SD card) and make it appear as RAM.
At the very least, a way to monitor and control the amount of RAM in use would be good... but I fear the device will not be truly useful if they can't up the RAM allocation. (Does anyone know if the 10 megs is a soft limit or a hard limit? i.e., did they stick in 10 megs of old-style RAM in there in addition to the NVRAM, or is it a virtual RAM space implemented in software?)
The device is such a good one... but this really hobbles its usefulness..
\marc
|
|
|