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
If someone does not so much debug/track a process for optimization, but wants to understand what exactly is going on on a CPU over time (scheduler, interrupts or anything similar might behave different than you expect) it would help to be able to filter it accordingly.
Consider tracking the cpu-id in the data you collect to allow later filtering if needed?
The text was updated successfully, but these errors were encountered:
This makes a ton of sense, and is super easy to add. (we already add thread ID and thread name, which in the meantime might already be useful, but I agree cpu-id makes a ton of sense!)
If someone does not so much debug/track a process for optimization, but wants to understand what exactly is going on on a CPU over time (scheduler, interrupts or anything similar might behave different than you expect) it would help to be able to filter it accordingly.
Consider tracking the cpu-id in the data you collect to allow later filtering if needed?
The text was updated successfully, but these errors were encountered: