3 ms·
This is for educational purposes. Thanks for the tip on seeing how much time is spent on different stack frames. Your response has helped most definitely. Howev
by kunalpatel73 9y ago
This is for educational purposes. Thanks for the tip on seeing how much time is spent on different stack frames. Your response has helped most definitely. However, we want to take a deeper dive and be able to access nested async functions. We would like be able to specifically identify each function, and the time spent to execute each function, whether it be async or a nested async function. This would help for debugging purposes to be able to see which function is taking a while to process. Do you find this to be a feasible idea?
- arenaninja 9y agoBy "the time spent each function", how is that different from http://www.brendangregg.com/flamegraphs.html http://www.brendangregg.com/flamegraphs.html? The only thing I can think of is that typically the x axis in flamegraphs is sorted alphabetically and aggregated and you could instead try to do this chronologically and in isolation. I'm curious which workflows you think your approach would be well suited for. In my case, I was investigating a webpack build process and flamegraphs served me well because with over 2000 modules seeing the data in aggregate is actually helpful. Though if purely for educational purposes, you can always do this chronologically and focus on a subset if the running time is too long