I feel there are two goals here which are solved differently:

1. improve tracing of the node process from within which in most cases requires either some sort of hooks, monkey patching, addons or changes to core
1. simplify integration of system tool tracing which can be solved in user land in most cases

I created an issue to collect info about existing user land tools, some of which are addons that interface with v8 in order to pull out profiling info.

I'm mostly focusing on 2) ATM, which can be converters, parsers to consume output of perf, dtrace, system tap, etc. and plugins into tools like debuggers,

At the moment we have the following (some rather new): I'm most likely missing lots, so please add some you know of

v8-lldb and lldb-jbt lldb plugins which add JS symbols info to stack traces
resolve-jit-symbols to add JS symbols info to any trace via info emitted by v8 when using the --perf-basic-prof flag
flamegraph perl scripts and the in browser flamegraph app to visualize aggregate info about traces
to .cpuprofile converter from perf-script or dtrace results which allows analyzing these traces via Chrome DevTools the same way we can already for output of v8-profiler

For those interested, some of us are gathering in #ngin8 on IRC to discuss some of these efforts.
@paulirish and I were talking there about _sunburst_s - (think flamegraphs+) - and how to get them integrated with system tools.

So a wide scope to cover here, not sure if it makes sense to have this all in one group or if we should split it into one group for each section as outlined in 1) and 2).

Uh oh!

tracing working group #671

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions