Jump to content

Dalvik (software)

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Dsimic (talk | contribs) at 04:26, 21 March 2015 (→Architecture: Numbers smaller than ten should be spelled out; Double quotes are preferred). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Dalvik
Original author(s)Dan Bornstein
Repository
Operating systemLinux kernel
PlatformAndroid
TypeVirtual machine
LicenseApache License 2.0
Websitesource.android.com/devices/tech/dalvik/index.html
Dalvik Executable
Filename extension
.dex

Dalvik is a process virtual machine (VM) in Google's Android operating system that executes applications written for Android. This makes Dalvik an integral part of the Android software stack (in Android versions 4.4 "KitKat" and earlier) that is typically used on mobile devices such as mobile phones and tablet computers, as well as more recently on devices such as smart TVs and wearables.

Programs are commonly written in Java and compiled to bytecode for the Java virtual machine, which is then translated to Dalvik bytecode and stored in .dex (Dalvik EXecutable) and .odex (Optimized Dalvik EXecutable) files; related terms odex and de-odex are associated with respective bytecode conversions. The compact Dalvik Executable format is designed for systems that are constrained in terms of memory and processor speed.

Dalvik is open-source software. It was originally written by Dan Bornstein, who named it after the fishing village of Dalvík in Eyjafjörður, Iceland.[1][2]

An alternative runtime environment called Android Runtime (ART) was included in Android 4.4 "KitKat" as a technology preview.[3][4] ART replaces Dalvik entirely in Android 5.0 "Lollipop".[5]

Architecture

A comparison of Dalvik and ART architectures

Unlike Java VMs, which are stack machines, the Dalvik VM uses a register-based architecture that requires fewer, typically more complex virtual machine instructions. Dalvik programs are written in Java using the Android application programming interface (API), compiled to Java bytecode, and converted to Dalvik instructions as necessary.

A tool called dx is used to convert Java .class files into the .dex format. Multiple classes are included in a single .dex file. Duplicate strings and other constants used in multiple class files are included only once in the .dex output to conserve space. Java bytecode is also converted into an alternative instruction set used by the Dalvik VM. An uncompressed .dex file is typically a few percent smaller in size than a compressed Java archive (JAR) derived from the same .class files.[6]

The Dalvik executables may be modified again when installed onto a mobile device. In order to gain further optimizations, byte order may be swapped in certain data, simple data structures and function libraries may be linked inline, and empty class objects may be short-circuited, for example.

Being optimized for low memory requirements, Dalvik has some specific characteristics that differentiate it from other standard VMs:[7]

  • The VM was slimmed down to use less space.
  • The constant pool has been modified to use only 32-bit indices to simplify the interpreter.
  • Standard Java bytecode executes eight-bit stack instructions. Local variables must be copied to or from the operand stack by separate instructions. Dalvik instead uses its own 16-bit instruction set that works directly on local variables. The local variable is commonly picked by a four-bit "virtual register" field. This lowers Dalvik's instruction count and raises its interpreter speed.

According to Google, the design of Dalvik permits a device to run multiple instances of the VM efficiently.[8]

Android 2.2 "Froyo" brought trace-based just-in-time (JIT) compilation into Dalvik, optimizing the execution of applications by continually profiling applications each time they run and dynamically compiling frequently executed short segments of their bytecode into native machine code. While Dalvik interprets the rest of application's bytecode, native execution of those short bytecode segments, called "traces", provides significant performance improvements.[9][10][11]

Performance

The relative merits of stack machines versus register-based approaches are a subject of ongoing debate.[12]

Generally, stack-based machines must use instructions to load data on the stack and manipulate that data, and, thus, require more instructions than register machines to implement the same high level code, but the instructions in a register machine must encode the source and destination registers and, therefore, tend to be larger. This difference is primarily of importance to VM interpreters for which opcode dispatch tends to be expensive along with other factors similarly relevant to just-in-time compilation.

However, tests performed on ARM devices in 2010 by Oracle (owner of the Java technology) with standard non-graphical Java benchmarks on Java SE embedded seemed to show it to be two to three times faster than Android 2.2, which is the initial release to include a just-in-time (JIT) compiler.[13][needs update]

In 2012, academic benchmarks confirmed the factor of 3 between HotSpot and Dalvik on the same Android board, also noting that Dalvik code was not smaller than Hotspot.[14]

Furthermore, benchmarks performed on Android device still show (as of March 2014) up to a factor 100 between native applications and a Dalvik application on the same Android device.[15][original research?][improper synthesis?] Upon running benchmarks using the early interpreter of 2009, both JNI and native code showed an order of magnitude speed up.[16]

Licensing and patents

Main article: Oracle v. Google

Dalvik is published under the terms of the Apache License 2.0.[17] Google says that Dalvik is a clean-room implementation rather than a development on top of a standard Java runtime, which would mean it does not inherit copyright-based license restrictions from either the standard-edition or open-source-edition Java runtimes.[18] Oracle and some reviewers dispute this.[19]

On August 12, 2010, Oracle, which acquired Sun Microsystems in April 2009 and therefore owns the rights to Java, sued Google over claimed infringement of copyrights and patents. Oracle alleged that Google, in developing Android, knowingly, directly and repeatedly infringed Oracle's Java-related intellectual property.[20][21][22] In May 2012, the jury in this case found that Google did not infringe on Oracle's patents, and the trial judge ruled that the structure of the Java APIs used by Google was not copyrightable.[23][24] The parties agreed to zero dollars in statutory damages for 9 lines of copied code.[25][26]

On May 9, 2014, the Federal Circuit partially reversed the district court ruling, ruling in Oracle's favor on the copyrightability issue, and remanding the issue of fair use back to the district court.[27][28]

See also

References

  1. ^ Journal entry referencing the source of the name
  2. ^ "Google Calling: Inside Android, the gPhone SDK". onlamp.com. Retrieved 2008-02-05.
  3. ^ Sean Buckley (2013-11-06). "'ART' experiment in Android KitKat improves battery life and speeds up apps". Engadget. Retrieved 2014-07-05.
  4. ^ Daniel P. (2013-11-07). "Experimental Google ART runtime in Android KitKat can bring twice faster app executions". phonearena.com. Retrieved 2014-07-05.
  5. ^ Brad Linder (October 15, 2014). "What's new in Android 5.0 Lollipop?". liliputing.com. Retrieved October 15, 2014.
  6. ^ Bornstein, Dan (2008-05-29). "Presentation of Dalvik VM Internals" (PDF). Google. p. 22. Retrieved 2010-08-16.
  7. ^ Rose, John (2008-05-31). "with Android and Dalvik at Google I/O". Retrieved 2008-06-08.
  8. ^ Google (2009-04-13). "What is Android?". Retrieved 2009-04-19. {{cite web}}: |author= has generic name (help)
  9. ^ Ben Cheng; Bill Buzbee (May 2010). "A JIT Compiler for Android's Dalvik VM" (PDF). android-app-developer.co.uk. Google. pp. 5–14. Retrieved March 18, 2015.
  10. ^ Phil Nickinson (May 26, 2010). "Google Android developer explains more about Dalvik and the JIT in Froyo". androidcentral.com. Retrieved July 8, 2014.
  11. ^ "Nexus One Is Running Android 2.2 Froyo. How Fast Is It Compared To 2.1? Oh, Only About 450% Faster". 2010-05-13. Retrieved 2010-05-21.
  12. ^ Shi, Yunhe; Gregg, David; Beatty, Andrew; Ertl, M. Anton (2005-06-11). "Virtual Machine Showdown: Stack Versus Registers" (PDF). Retrieved 2009-12-22.
  13. ^ Vandette, Bob (2010-11-22). "Java SE Embedded Performance Versus Android 2.2". Oracle Corporation. Retrieved 2011-09-04. The results show that although Androids new JIT is an improvement over its interpreter only implementation, Android is still lagging behind the performance of our Hotspot enabled Java SE Embedded. As you can see from the above results, Java SE Embedded can execute Java bytecodes from 2 to 3 times faster than Android 2.2.
  14. ^ Hyeong-Seok Oh, Beom-Jun Kim, Hyung-Kyu Choi, Soo-Mook Moon (2012). "Evaluation of Android Dalvik virtual machine". Association for Computing Machinery. Retrieved 2014-03-23. In the JITC mode, however, Dakvik is slower than HotSpot by more than 2.9 times and its generated code size is not smaller than HotSpot's due to its worse code quality and trace-chaining code.{{cite web}}: CS1 maint: multiple names: authors list (link)
  15. ^ "Top AndEBench Scores". www.eembc.org. Retrieved 2014-03-23.
  16. ^ "Developing and Benchmarking Native Linux Applications on Android". Lecture Notes of the Institute for Computer Sciences, Social Informatics and Telecommunications Engineering. Springer Publishing. 2009-04-29. Retrieved 2014-03-23. The results show that native C applications can be up to 30 times as fast as an identical algorithm running in Dalvik VM. Java applications can become a speed-up of up to 10 times if utilizing JNI.
  17. ^ "Downloading the Source Tree - Android Open Source". Android.git.kernel.org. Retrieved 2012-06-07.
  18. ^ Stefano Mazzocchi (2007-11-12). "Dalvik: how Google routed around Sun's IP-based licensing restrictions on Java ME". Retrieved 2010-08-16.
  19. ^ Ed Bott (September 8, 2011). "The real history of Java and Android, as told by Google". ZDNet. Retrieved 2011-11-27. The definition of a "clean room" implementation is that the engineers writing the code have no direct exposure to the original, copyrighted material, including code, specifications, and other documentation. That's a problem for Google, as I noted in yesterday's post, because there is substantial evidence that the engineers working on the project had direct access to the copyrighted material.
  20. ^ "Oracle Sues Google Over Java in Android Devices". digitaltrends.com. 2010-08-13. Retrieved 2011-08-08.
  21. ^ James Niccolai (2010-08-12). "Oracle sues Google over Java use in Android". Computerworld. Retrieved 2010-08-13.
  22. ^ Mark Hachman (2010-08-13). "Oracle Sues Google Over Android Java Use". PC Magazine. Ziff Davis.
  23. ^ Josh Lowensohn (May 23, 2012). "Jury clears Google of infringing on Oracle's patents". ZDNet. Retrieved 2012-05-25.
  24. ^ Joe Mullin (May 31, 2012). "Google wins crucial API ruling, Oracle's case decimated". Ars Technica. Retrieved 2012-06-01.
  25. ^ Niccolai, James (June 20, 2012). "Oracle agrees to 'zero' damages in Google lawsuit, eyes appeal". Retrieved 2012-06-23.
  26. ^ Adam Outler (May 16, 2012). "Update on the Oracle Versus Google Trial". Retrieved 2013-01-18. A major portion of the Oracle's claims are based on 9 lines of code contained within Java.Util.Arrays.rangeCheck(). Here is the code in question:...
  27. ^ Rosenblatt, Seth (May 9, 2014). "Court sides with Oracle over Android in Java patent appeal". CNET. Retrieved 2014-05-10.
  28. ^ "ORACLE AMERICA, INC. , Plaintiff - Appellant, v. GOOGLE INC., Defendant - Cross - Appellant" (PDF). Court of Appeals for the Federal Circuit. May 9, 2014. Retrieved 2014-05-10.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Dalvik_(software)&oldid=652833408"