Android Dalvik CPU. CPU Load Analysis Using Dalvik Bytecode on Android

Size: px

Start display at page:

Download "Android Dalvik CPU. CPU Load Analysis Using Dalvik Bytecode on Android"

Francis Lloyd
5 years ago
Views:

1 Android Dalvik CPU Dalvik Android CPU Dalvik CPU CPU CPU CPU CPU Load Analysis Using Dalvik Bytecode on Android Takashi Majima, 1 Tetsuo Yokoyama, 2 Gang Zeng, 1 Takeshi Kamiyama, 3 Hiroyuki Tomiyama 1 and Hiroaki Takada 1 We present a CPU load analysis method on Android platform by using hardware-independent trace information of Dalvik bytecodes. For the purpose of analysis, methods for generating and executing micro-benchmarks which issue the sequence of each Dalvik bytecode are introduced. The experimental results showed that the CPU load of micro-benchmarks was largely affected by the types arguments of bytecodes. Specifically, the variation of CPU load was up to 67 times over the types and 10 times over the arguments of given bytecodes. Therefore, not only the number of issued bytecode but also the types of bytecode and given arguments should be considered to construct an accurate CPU load model. Through a case study, the effectiveness of our approach for reducing CPU load has been validated. 1. CPU CPU CPU CPU Android 5) Dalvik DalvikVM Java Java Android CPU CPU 2. Java JVM Binder 2) JVM JVMPI JVM Profiler 1, Graduate School of Information Science, Nagoya University 2, Faculty of Information Sciences and Engineering, Nanzan University 3 NTT, Research Laboratories, NTT DOCOMO, Inc. 1

2 Interface JVMTI JVM Tool Interface Java DalvikVM JProfiler 4) DalvikVM 3) Java CProf 3.3% CPU 3) Albert Java 1) CPU Android Java Java JVM DalvikVM Dalvik Java DEX class Dalvik CPU 3. CPU Dalvik CPU CPU CPU CPU CPU CPU 1.0E E E E E-06 CPU load 1.0E E E E E E-06 Num of loop 1.0E E E E E E E E E E E+08 Num of bytecode in a single loop 1 Android Dev Phone 1 1 CPU Fig. 1 CPU load for a single bytecode on Android Dev Phone E E E E E E-06 1 CPU CPU CPU Dalvik CPU CPU Dalvik smali 8) Dalvik CPU CPU 1 ADP1 move 1 CPU CPU

3 1 Dalvik Table 1 Dalvik bytecode families Opcode Mnemonic Purpose 00 nop Waste cycles 01-0c move* Move between registers 0d,27 throw,... Exception handling 0e-11 return* Return from a method 12-1c const* Constants to registers 1d-1e monitor-* Synchronization 1f-20 chech-cast, instance-of Type checking 21,23-26 *array* Array manipulation 22 new-instance Instance creation 28-2c,32-3d goto*,if-*,... Execution control 2d-31 cmp* Comparations aget*,aput* Read/write array elements 52-5f iget*,iput* Read/write member fields 60-6d sget*,sput* Read/write static fields 6e-72,74-78 invoke* Method invocation 7b-80,90-e2 add-*,mul-*,... Operations 81-8f *-to-* Type conversion 73,79-7a,e3-ff (unused) CPU 4B KB ADP1 32KB CPU % CPU System.currentTimeMillis() UTC CPU 4.2 CPU 3 SciMark 2.0 7) 5 Linpack Embedded CaffeineMark 3.0 6) 6 SciMark CPU 5 CPU SciMark Linpack 5. CPU 5.1 Android HTC Android Dev Phone 1 ADP1, Atmark Techno Armadillo-500 FX, Nokia N810 2 PC USB Android SDK adb shell CPU /proc/stat 100 CPU Java CPU 5.2 CPU CPU 2 3

4 & '(!" $# %!$ %! "! # "! # ' ( & "'#!! %& $! " $ $! " #! (a) SciMark 2.0 (b) Linpack (c) Embedded CaffeineMark Dalvik Fig. 2 Issued Dalvik bytecode percentages. 2 Table 2 Processor specification of each platform Target Android Dev Phone 1 Armadillo-500 FX N810 Processor Qualcomm MSM7201A Freescale i.mx31 TI OMAP 2420 CPU ARM1136EJ-S ARM1136JF-S ARM1136 Clock 528 MHz 532 MHz 400 MHz D / I cache 32 KB/32 KB 16 KB/16 KB 32 KB/32 KB L2 cache 128 KB SciMark Linpack Embedded CaffeineMark SciMark CaffeineMark 10 3 CPU JVM/x86 Java x86 JVM CPU Linpack CaffeineMark CPU CaffeineMark CPU JVM SciMark 2 CPU add, mul invoke CPU CPU x86 JVM DalvikVM JVM DalvikVM DalvikVM JVM JVM DalvikVM DalvikVM 5% CPU 4

5 JVM/x86 Emulator Atmark Techno Armadillo-500 Nokia N810 Android Dev Phone 1 3 CPU Table 3 Bytecode linearity against CPU load Bytecode CPU load Single Alternate 5000/5000 div-int cmpl-double const div-double double-to-long goto if-eq move neg-int not-int CaffeineMark3 Linpack SciMark2 3 CPU Fig. 3 CPU load of each benchmark in each hardware platform. 5.3 CPU CPU CPU 1 div-int 2 CPU CPU 5.3 CPU 5.0% CPU CPU 5.4 CPU CPU Dalvik CPU CPU Dalvik CPU CPU ADP1 CPU div-long(9e) 1.62e-06s CPU nop(00) 4.97e-08s 32.5 CPU N CPU long double 86, 8b, 9e-9f, ae-af52-5f 71 CPU nop b 32-3d int long double 7b-80, 91-e2 91-e2 CPU CPU 38-3d 63-6d 47-4a CPU CPU CPU CPU.937 5

6 1.8E E E E E E E E E E E E E E E E E E E E E+00 0x0 0x32 0x64 0x96 0xc8 Bytecode opcode 0.0E+00 0x0 0x32 0x64 0x96 0xc8 Bytecode opcode 0.0E+00 0x0 0x32 0x64 0x96 0xc8 Bytecode opcode (a) Android Dev Phone 1 (b) Armadillo-500 FX (c) N810 4 Fig. 4 CPU CPU load of each bytecode in each hardware device. CPU 1 CPU div-long(9e) rem-long(9f) 2 CPU CPU CPU CPU CPU CPU CPU CPU CPU 5.5 CPU CPU div-double r1, r2, r3 double r2 r3 r1 2 CPU [0, 64] CPU 2 (a) CPU (cmp-*,add/sub/mul-int/long) (b) CPU (*-float/double) (c) CPU (cmp?-*,div/rem-int/long) 3 5 Armadillo-500 (a) add-int 2 CPU (b) 6

7 0 8.0e e e e e e e e-08 Value of register Value of register 2 7.0e e e e e-09 Value of register 3 (divisor) Value of register 2 (dividend) 1.2e e e e e e e+00 Value of register 3 (divisor) Value of register 2 (dividend) 5.0e e e e e e e-08 (a) add-int (b) div-double (c) rem-double 5 CPU Fig. 5 CPU load variance caused by bytecode arguments. CPU div-double 2 CPU (c) rem-double 2 CPU CPU 2 CPU CPU div-double CPU CPU CPU (> ) CPU CPU div-double 2 0 CPU L div double 16 if r 3 is a multiple of 2 19 if r 2 = 0 or r 3 = 0 L div-double (r 2, r 3 ) = 30 if r 2 = r otherwise r 2, r 3 div-double div CPU 6 double, long, float, int CPU int, double 5 long CPU CPU CPU CPU 7

8 !! 5.6 " #$% " #$% #& ' " #$% ()&* " #$% +(), " )-. (/ ' Fig. 6 6 CPU CPU load variance caused by numeric types. 2 CPU SciMark double float CPU SciMark double 25% 2(a) double float CPU 30-90% 4(a) SciMark double float CPU 8-25% CPU 15% long x 2 ( 1 ) 2 double (double)(x / 2) ( 2 ) double 2 (double)x / 2 CPU double long 2 6 (2) CPU 2.85 CPU 6. Dalvik Android CPU Android Dev Phone 1, Armadillo-500 FX N810 1 CPU CPU CPU CPU CPU 1) Albert, E., Arenas, P., Genaim, S., Puebla, G. and Zanardini, D.: Cost Analysis of Java Bytecode, European Symposium on Programming, pp (2007). 2) Binder, W., Hulaas, J., Moret, P. and Villazon, A.: Platform-independent Profiling in a Virtual Execution Environment, Software Pract. Exper., Vol.39, No.1, pp (2009). 3) Binder, W., Schoeberl, M., Moret, P. and Villazon, A.: Cross-profiling for Embedded Java Processors, Proc. International Conference on Quantitative Evaluation of Systems, pp (2008). 4) ej technologies: JProfiler. overview.html. 5) Google Projects for Android. 6) Pendragon Software Corporation: CaffeineMark ru/cm30/. 7) SciMark ) smali. 8

9 SciMark CaffeineMark JVM/x86 Emulator Atmark Techno Armadillo-500 Nokia N810 Android Dev Phone CaffeineMark3 Linpack SciMark2 (a) JVM/x86 Emulator Atmark Techno Armadillo-500 Nokia N810 Android Dev Phone SciMark2 Linpack CaffeineMark3 (b) 3 CPU Fig. 3 CPU load of each benchmark in each hardware platform.

A Quantitative Evaluation of the Contribution of Native Code to Java Workloads

A Quantitative Evaluation of the Contribution of Native Code to Java Workloads Walter Binder University of Lugano Switzerland walter.binder@unisi.ch Jarle Hulaas, Philippe Moret EPFL Switzerland {jarle.hulaas,philippe.moret}@epfl.ch