Originally Posted by mtotho
Dalvik isn't a cache, it has to do with the way programs are compiled and run. Don't quote me but dalvik uses a JIT compiler (just in time). This means that it initially compiles all programs to a byte code (not quite machine code). When it runs a program it only needs to compile to machine code the piece of the byte code that pertains to that part of the program. This affords a smaller memory footprint and faster app installs but requires more CPU bursts to compile byte code on the fly. This increased CPU usage also leads to poorer battery life (in theory) and sometimes choppiness in the app (like when scrolling). ART on the other hand, from what I can tell is a bit more like a standard non JIT runtime. All apps are fully compiled to machine code when installed, which takes longer to install, but less CPU is required to run the app later. The fully compiled program needs to be loaded into memory which is why ART uses more physical memory when apps are running (correct me if I'm wrong). Not further compiling is needed, saving CPU bursts.
Sent from my Nexus 7 using xda app-developers app
So in idiots terms, dalvic means more cpu, less ram needed? and ART is the opposite? More Ram less cpu,
soo isnt the benefit gona be there for some and not for others depending on the apps they use? So is there any real difference most causal users would notice? I understand maybe some battery life but not sure comparing results in here looks like 30 min better, not much. And compatibility is my biggest worry.
Rocking out on many phones: Current: Droid Razr Maxx HD, JB, Rooted, UNLOCKED
Tablet: Nexus 7 (2013) Unlocked, Rooted
Backup: Droid OG Razr, MAXX (conversion) CRACKED x2 Rooted, JB leak,
Ancient: Samsung Galaxy Prevail (1st boost mobile android)
Apple: iPod touch 5th gen iOS 7.0 Jailbreak trials in progress