> You have to store the compiled output somewhere. If you do a "df" on > a G1 you'll see that we're up against the wall on /system
OK, good point, but I thought this was really a problem with the G1 hardware only and future Android phones (like the Magic) would have a lot more internal storage? I suppose the RAM is a bigger problem. A 3-4x blowup in working set would indeed hurt. I read that the Sun JVM needs to keep a lot of bookkeeping data around in RAM because it has to be able to "uncompile" code at any time thanks to dynamic code loading. Being able to load classes generally removes a lot of optimization potential, will Dalvik have a way to opt out (or preferably opt in) for this feature to get tighter code? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "android-framework" group. To post to this group, send email to android-framework@googlegroups.com To unsubscribe from this group, send email to android-framework+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-framework?hl=en -~----------~----~----~----~------~----~------~--~---