Thanks for the amazing video. Any idea how Tracecompass builds a critical path analysis for a thread. When I look at the order of kernel events they map to the control flow view and not critical flow view. Would be great to know how Tracecompass deduces it from trace events?
You can look in the source code, it's open source. But basically the linux kernel is well instrumented. We know stuff like sched wakeup, switch etc.. and we can get more data like syscalls for files and network access. I cannot go into too much detail in a youtube comment, but reach out to the community @ tracecompass.org for a better deep dive!
Thanks for the amazing video. Any idea how Tracecompass builds a critical path analysis for a thread. When I look at the order of kernel events they map to the control flow view and not critical flow view. Would be great to know how Tracecompass deduces it from trace events?
You can look in the source code, it's open source. But basically the linux kernel is well instrumented. We know stuff like sched wakeup, switch etc.. and we can get more data like syscalls for files and network access. I cannot go into too much detail in a youtube comment, but reach out to the community @ tracecompass.org for a better deep dive!