Friday, May 1, 2015

Google and ARM are working on compiler that allows Android apps to 40% faster – Techzine

With the presentation of Android 4.4, Google introduced the ART-compiler, a new way to create Android apps so they can be quickly implemented on Android devices. With Android 5.0, this new ART compiler default. Now Google is working with ARM to a faster compiler called Optimizing.

Android compared to iOS and Windows certainly not the fastest operating system, in recent years, however, Google has put great steps which to improve. The main problem lies in the way in which the Java code is going to be formed into an application through the compiler. Android 5.0 was used in Android made the Dalvik compiler, it is now replaced by Android Runtime (ART). The big difference is that Dalvik on-demand code did compile and ART is not doing it right when installing an app.

ART but are still different parts of Dalvik process which Google has not yet know improve. Google is now teamed with chip designer ARM to further improve the new ART-compiler and optimize the old Dalvik parts too. This new compiler is called Optimizing offers include improved support for ARM’s 64bit AArch64 architecture.

Allegedly Optimizing already able to get some Android benchmarks 40 percent faster to perform. However, it would compile an app take a little longer (8 percent) and the file would have increased by 10 percent. These are two minor drawbacks which companies could potentially still be polished, but otherwise the drawbacks are arguably worth the benefit. The innovation in storage chips in recent years been extremely hard, prices have fallen and the average storage capacity has gone up, including mobile processors are getting faster.

When the new Google Optimizing Compiler wishes to apply in Android is still unclear. Probably a beta version will appear first before the new compiler is enabled by default. In late May find Google I / O location, Google’s own conference, the new compiler is then presented to developers and possible.

LikeTweet

No comments:

Post a Comment