> you should be able to mmap files rather easily in Java, and the file size is > not accounted for in the heap limit if I remember correctly...
I believe this is correct. Since a memory mapped file can be easily unmapped and remapped, its memory is fairly free for reuse. Cheers, Justin Android Team @ Google On Jun 14, 6:05 am, Digit <[EMAIL PROTECTED]> wrote: > can't you use the filesystem instead to act as a cache between your app and > the server ? > you should be able to mmap files rather easily in Java, and the file size is > not accounted for in the heap limit if I remember correctly... > > On Fri, Jun 13, 2008 at 12:48 AM, Shawn McMurdo <[EMAIL PROTECTED]> > wrote: > > > This is disappointing. > > > I have speech synthesis and streaming media analytics applications that > > would benefit from having access to more local memory. > > > With a 16M limit, it forces me to restructure applications to be more > > server dependent in ways that are less efficient and would not be necessary > > as mobile devices with more memory become available. > > > Perhaps an application descriptor could be added that would allow an > > application to use more memory. > > > That way the default would still be a 16M mmap for all other apps. > > > Any chance of incorporating something like this into 1.0? > > > Thanks. > > > Shawn > > > --==--==-- > > Shawn McMurdo > > See my Low Vision Guide at > >http://lowvisionguide.org > > > ----- Original Message ---- > > From: hackbod <[EMAIL PROTECTED]> > > To: Android Developers <android-developers@googlegroups.com> > > Sent: Thursday, June 12, 2008 2:02:27 PM > > Subject: [android-developers] Re: 16M Memory Limit > > > The 16MB is not a hard limit built in to the APIs, it is a current > > limit based on the hardware we are actually running on. It is also a > > little tricky to raise the limit, because it would require making the > > VM's garbage collector smarter in how it manages memory: right now it > > mmaps a memory region that is this maximum size, so if we make that > > maximum larger we can start running out of address space. This is > > something that can be fixed relatively easy (again it is not baked > > into the APIs), but won't be done for 1.0. > > > On Jun 12, 1:22 am, whitemice <[EMAIL PROTECTED]> wrote: > > > >>...On top of this, by the time Android is fully loaded on a 64MB device > > only 10-20MB of RAM will probably remain.* So, essentially your application > > would use all system resources...<< > > > > "640K ought to be enough for anybody" > > > - Bill Gates (apparently) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] Announcing the new M5 SDK! http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
