Performance analysis using Systrace

on YouTube ↗05m

" summary

Systrace is used to collect CPU time slices and reveals concrete fixes: three trampoline activities add about 160 ms to startup, inflating a drawer view costs ~42 ms, and a lock labeled as monitor contention (from Realm) accounts for ~30 ms. Tracing also shows background threads doing blocking I/O that overlap UI work and sum to 107 ms of wait time. Traces come from running the systrace tool from the catapult repo and viewing the generated HTML to pinpoint and quantify each opportunity.

AI-written summary · about

" chapters (5)

1. 0:00Intro
2. 0:30What is Systrace
3. 1:07First app
4. 2:08Second app
5. 4:27Conclusion

" related talks

• 42mDebugging Application PerformanceCarmen Jackson · droidcon San Francisco 2018
• 37mSystrace for gamesTim Murray · Android Game Developer Summit 2018
• 42mHow Much Is Tracing? Measuring the Overhead Caused by the Tracing InfrastructureAndreas Klinger · Embedded Linux Conference (ELC) @ EOSS 2023
• 54mUnderstanding Performance w/DTrace (While The Customer Yells)...A. Leventhal · Philly ETE 2016
• 48mCyclictest latency, find out why with tracingSteven Rostedt · Real Time Linux Summit @ Embedded Open Source Summit 2023
• 11mFinding out what's really going on, with DTrace!Colin Jones · !!Con 2016
• 12mStriaTrace: Efficient Tracing and Diagnosis for Online LLM InferenceEnnan Zhai, Erci Xu, Jingren Zhou, Kun Qian, Xue Li, Wenyuan Yu, Guangtao Xue, Yanqing Chen, Haonan Wu, Jingbo Xu · 20th USENIX Symposium on Operating Systems Design and Implementation (OSDI '26)
• 52mTracking Down What Happened: A Comparison of Tracing SolutionsJohn Ogness · Open Source Summit + Embedded Linux Conference + OSPOCon 2021