Slides - jtres 2012

More documents

Recommendations

Info

We believe Dalvik’s trace-based JITC has a severeperformance problem in its current form We do not experience any critical problem in running the Android apps, though• Dalvik portion in the total running time is not dominant Android apps lack hot spots unlike benchmarks• Requiring a faster warm spot detection or ahead-of-timecompilationVirtual Machine & Optimization Lab34
Page 4: VM for executing Java in Android pl
Page 11 and 12: Java Source Codepublic static int f
Page 13 and 14: 2.521.510.50Chess kXML Parallel PNG
Page 15 and 16: 2.521.510.50Chess kXML Parallel PNG
Page 17 and 18: 1.81.61.41.210.80.60.40.20Chess kXM
Page 19 and 20: How many times a Dalvik bytecode is
Page 21 and 22: 86.00%75.00%654.00%43.00%32.00%211.
Page 23 and 24: Low code quality due to short trace
Page 25 and 26: 100%80%60%40%20%0%Native Native app
Page 27 and 28: Garbage collection (GC) portion is
Page 29 and 30: Numbers are log scale 1000000010000
Page 31 and 32: 500450400350300250200150100500App t
Page 33: Loading time only 1.21.110.90.80.7A

Slides - jtres 2012

Create successful ePaper yourself

Delete template?

Save as template?