Systrace for games
summary
Systrace + Catapult gets kernel-level timelines showing exactly what runs, when and why, with sub-1% overhead and per-CPU ring buffers (about 1 MB ≈ 2 s). Android P adds a Quick Settings recorder that saves compressed traces requiring post-process via from_file processing. Adding app-side sections (Trace.beginSection / ATrace_beginSection) reveals causation: e.g., 1.4 s idle at startup, a 700 ms load gap from sound I/O, or a 5.7 s Unity level start split into 3.1 s run + 2.5 s sleeps.
AI-written summary · about
chapters (8)
- 0:00Intro
- 2:35Taking a trace
- 7:12Looking at a trace
- 12:06Different states
- 14:12Aggregate view
- 17:59Game traces
- 22:57Frame lifecycle
- 30:21Gameplay
related talks
42mDebugging Application Performance
05mPerformance analysis using Systrace
37mFrom Systrace to Safetynet: Android game development case studies
33mUI profiling in examples. Where is my bottleneck?
38mA Busy Android App Developers' Guide to Perfetto
35mIn Search of Performance: the Subtle Art of Android Profiling
27mIntroducing the Mobile PerfSDK
31mImprove app performance with Android Studio Profilers