perfetto

I wanted to take a look at some of these bug fixes, and one of the linked ones [1] seems more like a feature to me. So maybe it should be the week of "low priority" issues, or something like that. I don't mean to sound negative, I think it's a great idea. I do something like this at home from time to time. Just spend a day repairing and fixing things. Everything that has accumulated. 1: https://github.com/google/perfetto/issues/154

> Yes I know, I used to work on Android ;) Ahhhh good to know :D > If it would help, I am of course happy to file bugs and also make simple fixes :) Please yes do file bugs! It's so useful to have these things tracked: I think you've already given several great pieces of feedback in your comment, it would be really nice to have this tracked. Doubly so if you have screenshots/videos/descriptions of other profilers (e.g. instruments) and how they do things so we can learn from their UX as well! And of course, if you're willing to contribute, we would love to have them! We have a decent contributor base today but it's something I want to continue growing and investing in over time! > can do something like get an "activity view" (like the stack that shows how many tasks are active) across all tracks I think you're asking for basically the sa

> I don't suppose there is some supported way to inject macros or "ui automation" [1] into the iframe? This is exactly what https://github.com/google/perfetto/issues/1342 is about :) It's not the highest priority issue but it is something I want to implement sooner than later. Oh and separately you're right we should add support for also passing macros over the postMessage API. Will file a bug for this.

Perfetto does support embedding though I concede it's not as seamless as it was with chrome://tracing. As with Chrome://tracing, you can put the UI inside an iframe and pass the trace to the UI via postMessage (see https://perfetto.dev/docs/visualization/deep-linking-to-perf...). There are quite a few people that do this: the big ones I'm aware of is the Rust language CI for performance (https://github.com/rust-lang/rustc-perf/issues/1857) and Flutter Devtools (https://github.com/flutter/devtools/pull/4386/files). There's also an effort via contributions from some external folk to add more "proper" support for embedding (i.e. compiling Perfetto directly into a larger application, more like a library). That discussion is happening at https://github.com/google/perfetto/pull/2267 and the PRs spawned off it. We're hoping to have some more pub

Please file bugs against us at https://github.com/google/perfetto/issues! We're always very interested in seeing traces which are hitting performance issues. We take them seriously and are responsive at fixing them (or at least explaining what makes it hard to fix). As I note in the post, we optimize for the needs of Android/Chrome developers so we may not necessarily know about whatever condition you are hitting with your trace!

Thanks for the nice words! Your tool sounds super neat! We're look at integrating some sort of similarish things into Perfetto itself where, for a synthetically generated trace, you can say "run this SQL query and add a debug track for it on trace load". See the discussion on https://github.com/google/perfetto/issues/1342 :)