J2ME memory usage -vs- recordstore access time

D

dutone

since writein' large records to a RecordStore can be time consuming,
would anyone advise cachein' data to avoid so many reads? (Assuming
that the app. wanted to minimize to long delays) Maybe network reads
could be cached too. But then the cache would have to be somewhat
restricted given the limited memory of many devices, and could impose
a burden of the app its self if it got to big. Efficent managment of
the cache across platforms could become complex and a project withen
its self.
Any thoughts.....
 
D

Darryl L. Pierce

dutone said:
since writein' large records to a RecordStore can be time consuming,
would anyone advise cachein' data to avoid so many reads? (Assuming
that the app. wanted to minimize to long delays)

My experience has been that RMS on alot of devices is painfully slow. If you
have to go to RMS a lot then yes it's a better trade off to cache some data
in memory. If, however, you only pull data infrequently then I wouldn't
waste the precious heap space on caching.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
474,432
Messages
2,571,680
Members
48,796
Latest member
Greg L.

Latest Threads

Top