Douglas Handy wrote:
And methinks therein lies the rub on why the initial implementation of the cache
prioritization routines could not simply be taken from disk based systems. Apps
which use frequent storage heap manipulations (due to previous limits in dynamic
memory and the fact there historically was a very minimal performance impact for
using storage heap) are bound to run into issues when PDAs start using actual
disk drives.
It's not really that different from a memory-mapped file on a system
with virtual memory. Yes, performance may suffer in certain circumstances,
but if you have 32 MB of RAM and a good algorithm to manage it, then
it shouldn't be any worse than devices that have 32 MB of storage heap
to begin with, with the tiny exception of applications that sense the
size of the storage heap and try to use as much of it as possible on
the assumption that all of it is fast.
OTOH, if you look at how much dynamic heap is available on the T5, you shouldn't
need to use storage heap anymore for many of the things you did in the past.
Yes, although if you are trying to write portable code, the problem is
that some OS 5 devices have very little dynamic heap and a lot of fast
storage heap, whereas the T5 and some other have lots of dynamic heap.
So, that makes it a tad bit harder.
IMHO, the change to
non-volatile storage is actually very welcome and in the long term may *improve*
the perceived relability of the devices because the data won't be lost simply
due to battery depletion.
Especially on phones, where many people have a habit of talking and
talking until the battery is bone dry. Personally, I don't do this,
but lots of regular people do.
- Logan
--
For information on using the Palm Developer Forums, or to unsubscribe, please
see http://www.palmos.com/dev/support/forums/
