Linked by Thom Holwerda on Tue 10th Jul 2012 17:08 UTC
PDAs, Cellphones, Wireless I've been flashing CyanogenMod 9 nightlies for months now, and the process to do so has become pretty much muscle memory at this point (if cwm ever changes its menu order I'm screwed). One step of this process has always fascinated me simply because I have no idea what exactly it does and why I have to do it: clearing Dalvik cache.
Thread beginning with comment 526241
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Comment by anevilyak
by fatjoe on Tue 10th Jul 2012 18:19 UTC in reply to "Comment by anevilyak"
fatjoe
Member since:
2010-01-12

The word you are searching for is AOT compilation cache.

(the android cache partition also contains some data)

Reply Parent Score: 4

RE[2]: Comment by anevilyak
by anevilyak on Tue 10th Jul 2012 20:24 in reply to "RE: Comment by anevilyak"
anevilyak Member since:
2005-09-14

Will try to remember that, thanks!

Reply Parent Score: 2

RE[2]: Comment by anevilyak
by JAlexoid on Wed 11th Jul 2012 13:20 in reply to "RE: Comment by anevilyak"
JAlexoid Member since:
2009-05-19

Not necessarily. Dalvik doesn't do AOT compilation. It does do resource optimization and layout formats.

Reply Parent Score: 3

RE[3]: Comment by anevilyak
by pgeorgi on Wed 11th Jul 2012 16:30 in reply to "RE[2]: Comment by anevilyak"
pgeorgi Member since:
2010-02-18

Dalvik doesn't do AOT compilation.

Though it definitely would be nice to add that.. There's no need to re-JIT the on-screen keyboard task every time it's loaded...

Having the code mmapped also reduces strain on the memory management (since filebacked mappings can be dumped to storage easily).

Would also create opportunities for expensive optimizations which could be scheduled for when the device is "asleep" and externally powered.

Essentially FX!32 for Dalvik.

Reply Parent Score: 2