The time it takes between java edit and final apk feels like it has regressed a lot in the past year.
I took a trace when making a base_java edit that didn't touch any public apis via https://github.com/nico/ninjatracing and have attached it here.
Things that stood out to me:
* 14s for gen/chrome/browser/android/chrome_jni_registration.h
* All bytecode-rewritten.jar files recreated. These should be skipped when interface jar doesn't change
* Apk finalization took >20s. Should look to see if this was from signing, and use cached signatures if it's not already leveraging them.
The time it takes between java edit and final apk feels like it has regressed a lot in the past year.
I took a trace when making a base_java edit that didn't touch any public apis via https://github.com/nico/ninjatracing and have attached it here.
Things that stood out to me:
* 14s for gen/chrome/browser/android/chrome_jni_registration.h
* gen/media/base/android/media_java.javac.jar was listed as a job. It shouldn't need to re-run at all.
* All bytecode-rewritten.jar files recreated. These should be skipped when interface jar doesn't change
* Apk finalization took >20s. Should look to see if this was from signing, and use cached signatures if it's not already leveraging them.
Comment 1 by agrieve@chromium.org
, Feb 9 2018387 KB
387 KB View Download