diff options
| author | James M Snell <jasnell@gmail.com> | 2018-05-15 00:24:58 +0300 |
|---|---|---|
| committer | James M Snell <jasnell@gmail.com> | 2018-05-17 00:34:41 +0300 |
| commit | 8630eea1717811523cd4333f0310f93eb2068d73 (patch) | |
| tree | e758c6afab4309fac945467656545bc9909dbbe5 /doc/api/tracing.md | |
| parent | 2183b256c2ee80abb79bcfbb974b61bf380575e8 (diff) | |
vm,trace_events: add node.vm.script trace events category
Add basic trace events for node_contextify. These generally
align very well with V8.ScriptCompile and V8.ScriptExecute
trace events and provide good additional context. For instance,
using the node.vm.script trace category at startup allows us to
see exactly how long compilation and init of each of our core
modules adds to the startup time.
PR-URL: https://github.com/nodejs/node/pull/20728
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Ali Ijaz Sheikh <ofrobots@google.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Diffstat (limited to 'doc/api/tracing.md')
| -rw-r--r-- | doc/api/tracing.md | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/api/tracing.md b/doc/api/tracing.md index 228d3a66784..ca91b8aac78 100644 --- a/doc/api/tracing.md +++ b/doc/api/tracing.md @@ -24,6 +24,8 @@ The available categories are: * `node.perf.timerify` - Enables capture of only Performance API timerify measurements. * `node.fs.sync` - Enables capture of trace data for file system sync methods. +* `node.vm.script` - Enables capture of trace data for the `vm` module's + `runInNewContext()`, `runInContext()`, and `runInThisContext()` methods. * `v8` - The [V8] events are GC, compiling, and execution related. By default the `node`, `node.async_hooks`, and `v8` categories are enabled. |