You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unfortunately, perfetto UI does not order these processes by start time. It seems to order the processes by 'eventfulness' instead.
As a backup, I figured I would use the process_sort_index metadata item to re-order the processes as needed, however, perfetto UI does not respect that.
I see past issues where implementation of process_sort_index has been shot down. Is there an alternative you could suggest for this? Needing to order the processes chronologically is (I would imagine) a need for many projects adopting this UI.
The text was updated successfully, but these errors were encountered:
I don't think there's any suggestion for now. Having arbitrary sorts at the UI level might be something supported at some point but is not a priority.
Our priority is first features for native Perfetto traces (especially Android system tracing). If our project is used in other ways, we're very happy with that but it's not our focus.
Hi,
My team is working on a project that generates a flow of timed events in a system. I am using the trace event format as described here: https://docs.google.com/document/d/1CvAClvFfyA5R-PhYUmn5OOQtYMH4h6I0nSsKchNAySU/preview.
Each of these events is described as a process in the JSON file.
Unfortunately, perfetto UI does not order these processes by start time. It seems to order the processes by 'eventfulness' instead.
As a backup, I figured I would use the process_sort_index metadata item to re-order the processes as needed, however, perfetto UI does not respect that.
I see past issues where implementation of process_sort_index has been shot down. Is there an alternative you could suggest for this? Needing to order the processes chronologically is (I would imagine) a need for many projects adopting this UI.
The text was updated successfully, but these errors were encountered: