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
The profile.proto data format does not have a specific way to note which process a sample came from. However, perf.data files tend to include samples from multiple processes.
When using pprof on perf.data files, it should be possible to determine which process a sample is from, and this should be displayed to the user.
The text was updated successfully, but these errors were encountered:
aalexand
changed the title
Make it possible to distinguish between samples in different processes which are part of the same profile.
Have a way to filter by process / command for perf.data-converted profiles
Jan 29, 2018
The profile.proto data format does not have a specific way to note which process a sample came from.
The easiest would be using tags. The perf_data_converter currently has a way to add process ID tags as part of conversion, I believe. We should make it so it also knows how to add command name tags, and then configure the converter run to add those tags. This will allow using tag filtering to filter by a specific process.
@lannadorai Maybe you are the right owner for this after all. I think what we want here is make the perf data file conversion produce the process name / command label so that pprof can be used to filter by that tag.
The profile.proto data format does not have a specific way to note which process a sample came from. However, perf.data files tend to include samples from multiple processes.
When using pprof on perf.data files, it should be possible to determine which process a sample is from, and this should be displayed to the user.
The text was updated successfully, but these errors were encountered: