Demystifying Baseline Profile
summary
Baseline profiles get read from APK assets, transcoded to match the device profile version, and write baseline profile at startup via the profile installer initializer or a broadcast receiver that performs a synchronous write. Macrobenchmark prep broadcasts that intent then runs adb shell cmd package compile to force AOT compilation into speed profile mode. Validation requires checking the runtime compile state and watching for failures such as OEM-locked ADB or battery optimizations that make package compile flaky.
AI-written summary · about
chapters (12)
- 0:00Introduction to baseline profiles
- 1:17What baseline profiles do
- 3:07Profile installer explained
- 8:17Writing profiles at startup
- 10:51Broadcast receiver in profile installer
- 11:57Macrobenchmark library overview
- 13:22Preparing app for testing
- 16:35Dogfooding workflow issues
- 19:05App preparation for testing
- 21:58Package compile command failures
- 24:06Google Play distribution expectations
- 25:53Summary and Q&A
related talks
40mMy Journey: Adding Baseline Profiles to a Production-Based Android App: Success or Failure?
34mMaking apps blazing fast with Baseline Profiles
20mMaking apps blazing fast with Baseline Profiles
01h 00mThe Basics of Profiling
28mMaking apps blazing fast with Baseline Profiles
01h 17mThe Basics of Profiling
51mProduction Profiling: What, Why and How
39mProfiling and Benchmarking 101