On Fri, Nov 26, 2010 at 9:56 AM, Stuart McCulloch <[email protected]> wrote:
> This is incorrect. >> >> Dalvik was created first and foremost for technical reasons. Dan explained >> some of these in this >> post<http://android-developers.blogspot.com/2010/05/dalvik-jit.html>, >> but in a nutshell, the traditional JVM model is not well suited for embedded >> development and Dalvik addresses this by focusing on very selective >> compilation, aggressive memory optimizations, power consumption awareness >> and a strong emphasis on multiprocesses and VM sharing. >> > > Indeed, the (micro-)benchmarks used in the original article don't > necessarily relate to real-world mobile applications. > > And interestingly the Dalvik VM beats the JavaSE Embedded VM in all the > "Strings" tests... so it's not all one-sided. > Right. The only way to really measure the effectiveness of a virtual machine on a phone is to actually run it within a real OS on a real phone. The patterns of usage by a regular user are impossible to capture in benchmarks. -- Cédric -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
