Hacker Newsnew | past | comments | ask | show | jobs | submitlogin
Make libart the default runtime (googlesource.com)
36 points by bbzealot on Feb 1, 2014 | hide | past | favorite | 11 comments


I've been using ART ever since KitKat came out for the Nexus 4, and have had no problems with it. It seems pretty stable.


Same here, works fine. Disclaimer: My brother works on it at Google :-)


But are there benefits?


I haven't measured, but it feels faster (some apps seem to load much faster, Wikipedia for example).


Apps should start faster, since they don't have to wait for the VM to identify hotspots and JIT them. This should also lead to reduced memory usage overall.


I'd guess ahead-of-time compilation means they can "afford" slower compilation times (i.e., a slow compile won't disrupt the flow of user in an app). And that would give them room to do more optimization. But that's totally a guess.


What does this mean? What is libart?



It's a new "runtime." I suppose they don't call it a VM because it's an ahead-of-time compiler. Dalvik is pretty efficient, so don't expect miracles, but ART is probably a good trade of space for speed.


I hope this only applies to apps targeting the next API version. As of now, Clojure apps have issues with ART:

https://groups.google.com/d/msg/clojure-android/J4cxkMRW2QA/...


Wow this is fantastic. Does it mean the next version of Android will have ART enabled by default?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: