Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Austin: Diagnostics #30

Closed
joshgav opened this issue Sep 13, 2016 · 11 comments
Closed

Austin: Diagnostics #30

joshgav opened this issue Sep 13, 2016 · 11 comments

Comments

@joshgav
Copy link

joshgav commented Sep 13, 2016

Transferring from nodejs/diagnostics#58

Some topics from that thread:

  • tracing: controller, protocol, format
  • async_hooks
  • es6 module patching
  • inspector protocol and tools

/cc @nodejs/diagnostics @watson

@danielkhan
Copy link

Adding

  • Event Loop metrics (pending tasks, tasks per second). More or less like Linux load.

@joshgav
Copy link
Author

joshgav commented Nov 17, 2016

From the November Diag WG meeting -

@joshgav
Copy link
Author

joshgav commented Nov 30, 2016

Several of us chatted yesterday and agreed to meet Friday for Diagnostics, allowing Thursday afternoon for participating with other groups etc. Any opposed please let us know here.

Let's flesh out the agenda a bit, the following is based on what's above and other evolving discussions:

  • TracingController

    • Adding trace points to core modules
    • JS API?
    • Intended use cases
  • Inspector - CLI Debugger

    • node-inspect in core itself or alongside it?
    • Opportunities for new capabilities available through inspector - specifically CPU and Heap profiling at the moment.

We may also want to discuss the UUID associated by Inspector with each process as in nodejs/node#9185.

/cc @nodejs/ctc in case some of you can join.

@Trott
Copy link
Contributor

Trott commented Nov 30, 2016

I'd like to be there for the Debugger stuff.

@Trott
Copy link
Contributor

Trott commented Nov 30, 2016

(Time?)

@jkrems
Copy link

jkrems commented Nov 30, 2016

I'd also like to join for the Debugger stuff.

@joshgav
Copy link
Author

joshgav commented Nov 30, 2016

@Trott

Time?

Going with #35, how about 9am? Meet near where the keynotes were and choose a room. We can review and set the agenda first thing. Perhaps we can spend a chunk of the time coding and presenting to each other.

@jkrems - Was counting on you coming! Thanks!

@danielkhan
Copy link

danielkhan commented Nov 30, 2016

I'll be there at 9am.

@jkrems
Copy link

jkrems commented Dec 1, 2016

@joshgav Side note - inspired by your talk today I added some quick profiler support to node-inspect:

debug> profile
# [...]
debug> profileEnd
[Profile 2572307μs]
debug> _.save('my.cpuprofile')
Saved profile to /path/to/cwd/my.cpuprofile
debug> takeHeapSnapshot('my.heapsnapshot')
Heap snaphost prepared.
Wrote snapshot: /path/to/cwd/my.heapsnapshot

@joshgav
Copy link
Author

joshgav commented Dec 2, 2016

Notes: https://docs.google.com/document/d/1hUiG1nv4hxjnznN2NjU3F-MzXtKhWxvMI3R8caJyzCs/edit

@joshgav
Copy link
Author

joshgav commented Dec 6, 2016

Great meeting everyone! Cooked notes in this PR: nodejs/diagnostics#76, PTAL.

@joshgav joshgav closed this as completed Dec 6, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants