Is there any doc where I can get the details of meaning of all the options and meaning of diffrent timelines like binder, ftrace at ui.perfetto.dev as I can't find properly in the offical doc. #1010
-
Basically I want a doc guide like Intelij Idea has see here https://www.jetbrains.com/help/idea/getting-started.html . I have searched all over the internet but I didn't get any proper guide for uses of all the options and meaning of different timelines. We're on our own to interpret the meaning by somehow. ![]() |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
So in general yes we do lack a full public explanation into all the pieces that make up a Perfetto trace collected on Android. There's a lot of content available internally inside Google (mainly recorded talks and informal presentations) but that's not been made public so for people outside Google, Perfetto can seem very mysterious. As a bit of context, Perfetto has historically been a power user tool. It was used by the low level systems engineers who really wanted to dive into performance and understanding the system. Over time we've improved to the tool to make it so that more people find it easier. However, there is still a missing piece which is what you describe: a breakdown of all the things that make up a trace and how best to use them to find and fix issues. Last quarter, I did spend a bunch of time working on such content for our docs website but unfortunately didn't get far enough to land it. I hope to get to it again some time this year. Also we're looking into starting a Perfetto blog where we can share information like this in a more "guided walkthrough" manner. We're hoping to have content from experts on the Android team who use Perfetto day in and out to provide insights into how they use Perfetto. For now the best I can offer is https://perfetto.dev/docs/quickstart/android-tracing and all the content in the sidebar under "data sources". I appreciate it's not quite in the right shape but there's a lot of useful information there. Eventually we'll get to a proper guide. |
Beta Was this translation helpful? Give feedback.
So in general yes we do lack a full public explanation into all the pieces that make up a Perfetto trace collected on Android. There's a lot of content available internally inside Google (mainly recorded talks and informal presentations) but that's not been made public so for people outside Google, Perfetto can seem very mysterious.
As a bit of context, Perfetto has historically been a power user tool. It was used by the low level systems engineers who really wanted to dive into performance and understanding the system. Over time we've improved to the tool to make it so that more people find it easier. However, there is still a missing piece which is what you describe: a breakdown of all …