![]() If you are just looking at diagnostics or errors, looking at the log with grep or your favorite text viewer should suffice. Why is it useful to have this logcat log supported in the tooling? ![]() So Perfetto is great for analyzing run-time perf after the system is booted, but currently doesn’t cover boot very well, even on the upcoming Android 13. The Perfetto tracing starts after kernel sometime in usermode, and only captures at best 1/2 to 1/3 of total boot. There is no Linux or Android deep tracing that I know of that covers kernel boot. The answer is yes Perfetto is great for deep level system tracing, but one shortcoming is that Perfetto doesn’t cover the boot scenario very well. Logcat is useful in general, but why do we find it useful for performance work? Don’t we already have an official performance tooling available with a full-featured and system-level Perfetto tracing? This is what the logcat log would look like when loaded in Windows Performance Analyzer (WPA) Logcat for performance Logcat is a text-based dump of system & app messages on Android. ![]() We recently added support for parsing Android logcat logs to the OSS Microsoft-Performance-Tools-Linux-Android project.
0 Comments
Leave a Reply. |