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
With clinic, https://github.com/nearform/node-clinic, we've been working on some new fun and interesting ideas on how to profile and visualize async flow. It's getting to a state where we'd love to share some of stuff we've made so far with the diagnostics WG to get some feedback. I believe @mcollina and @AndreasMadsen also presented a very early version of it at the last summit
Where each bubble represents async/sync time spent on operations. The line between the bubbles represents the flow, with longer lines meaning longer latencies. Most of this is powered by async_hooks and trace events.
Would love to do a short demo at the next WG meeting if possible, on Wed the 2nd of May :)
The text was updated successfully, but these errors were encountered:
Reminder @nodejs/diagnostics: if you want early access to this tool, reach out to @mafintosh or @mcollina.
I'm closing this issue since the tool was shown at the last meeting (congratulations btw, looks like a promising tool 😄). If you believe there's anything else to be discussed here feel free to reopen.
With clinic, https://github.com/nearform/node-clinic, we've been working on some new fun and interesting ideas on how to profile and visualize async flow. It's getting to a state where we'd love to share some of stuff we've made so far with the diagnostics WG to get some feedback. I believe @mcollina and @AndreasMadsen also presented a very early version of it at the last summit
The tool itself profiles code like this:
And turns into a UI like this:
Where each bubble represents async/sync time spent on operations. The line between the bubbles represents the flow, with longer lines meaning longer latencies. Most of this is powered by async_hooks and trace events.
Would love to do a short demo at the next WG meeting if possible, on Wed the 2nd of May :)
The text was updated successfully, but these errors were encountered: