Thread Id numbers in Perfetto UI

[Frederico Xavier]

Is it possible in the Perfetto UI to not print the thread Id numbers (in the left most, threads column)?

I put this pic attached.

[Hector Dearman]

Hi Frederico,

There is no way to hide the thread ids from the track names in the UI at the moment.

We plan to rework the track naming/grouping/sorting in the future so we will bear that in mind as a feature request.

Out of curiosity, why do you want to hide the thread ids? If people are confusing them with the names I guess we could change how they are styled in the UI.

Thanks,

Hector

On Wed, 4 Aug 2021 at 19:46, Frederico Xavier <fredxa...@gmail.com> wrote:

Is it possible in the Perfetto UI to not print the thread Id numbers (in the left most, threads column)?

I put this pic attached.

--
You received this message because you are subscribed to the Google Groups "Perfetto Development - www.perfetto.dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to perfetto-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/perfetto-dev/e3a82edf-f781-46ff-8121-460e8debcf24n%40googlegroups.com.

--

-Hector Dearman

[Frederico Xavier]

Hello Hector, thanks for the fast reply (and also congratulations on the Perfetto tool, it is quite amazing and useful!)

Just for some context: here at Matrox we're using Perfetto to debug computer vision driver events.

Out of curiosity, why do you want to hide the thread ids? If people are confusing them with the names I guess we could change how they are styled in the UI.

The reason that I want (in some cases) to hide the thread id is that (if you can see in the pic below)

1. I'm clustering events from several (kind of) related threads into a single "timeline" by using the metadata events ("cat": "__metadata"), so in these cases the thread id has no actual meaning per se... so it would actually be cleaner if I only displayed the "timeline" name, without the # (and indeed some people/users got confused on what the # meant in these cases)
2. In all other cases, the thread id is indeed quite useful (bottom part of the pic)
3. maybe there's a more elegant way to do this clustering events (I've read through the json trace event format, and up until now that's the best way I came up with... I'm completely open for suggestions =)

Thanks again!

Fred Xavier

--

Fred Xavier, MSc