Quote Originally Posted by tudyniuz View Post
Eu nu am simtit diferente folosindu-l, doar unele aplicatii care nu mai functionau.
Nu sunt doar diferente de performanta, ba chiar unii ar spune ca battery usage-ul e cel care a primit cel mai mare boost cu ART (vs Dalvik):
Battery life is the biggest difference I see with ART, which is something that should make any smartphone user happy. In our battery tests with the Nexus 5, I found that the phone was capable of getting you through a whole day as long as you only had the screen on for about three and a half hours total. This isn’t bad, but it’s also not great. With ART running I found that the screen on experience is still very much the same. If you’ve got more than three hours of screen on time, there’s a good chance your phone is almost dead. The difference is in how the phone consumes battery in an idle state. With ART running, the Nexus 5 could easily go a full 24 hours of idling and performing casual tasks, while with Dalvik running that same workload would only get the phone to 17 or 18 hours.


---------- Post added 27-11-2013 at 03:13 ----------

Or sa spuna multi ca iar compar cu iOS... dar de-abia cu ART incepe si Android sa treaca la viteza aplicatiilor compilate nativ, si nu interpretate "on the fly":
Google knows all this about Dalvik, of course, which is why it’s been working on its replacement — Android Runtime (ART) — for more than two years. An early version of ART is included with Android 4.4 and can be enabled in Settings > Developer Options > Select Runtime.

ART straddles an interesting mid-ground between compiled and interpreted code, called ahead-of-time (AOT) compilation. Currently with Android apps, they are interpreted at runtime (using the JIT), every time you open them up. This is slow. (iOS apps, by comparison, are compiled native code, which is much faster.) With ART enabled, each Android app is compiled to native code when you install it. Then, when it’s time to run the app, it performs with all the alacrity of a native app.

It obviously takes some time to perform the AOT compilation at install time, but the long-term gains from apps that load and run faster will easily make up for it. You probably won’t even notice the AOT compilation of small apps; but for larger apps, we’re talking about a noticeable delay. If you switch an existing device from Dalvik to ART, you’re talking about a wait time of a few minutes while Android performs AOT for all your installed apps.

The main advantage of ART is that it allows Android developers to continue writing the exact same code, and having their apps work across a wide range of hardware specs and form factors — but now their apps will now run significantly faster, feel more responsive, and your device’s battery life should improve. Early testing indicates that ART is twice as fast as Dalvik. ART’s compiled code should also perform more consistently than JIT Dalvik, too, reducing UI latency and stuttering. The biggest gains will probably be for computationally intensive apps, such as photo and video editors, but if this early build of ART is anything to go by, there should be significant improvements across the board. ART could be change that finally makes Android as responsive and snappy feeling as iOS.