diff options
| author | James M Snell <jasnell@gmail.com> | 2018-06-03 16:58:48 -0700 |
|---|---|---|
| committer | James M Snell <jasnell@gmail.com> | 2018-06-15 09:05:19 -0700 |
| commit | b55f6a0f010da7f2f812b0956283a1d58ebe1ff1 (patch) | |
| tree | 23d797e24b5b28ee26356ed7d36e5c1d2d5383c0 /doc/api/perf_hooks.md | |
| parent | 17e378b51a4e35533b43bae66e7aa76faaad17b3 (diff) | |
| download | node-new-b55f6a0f010da7f2f812b0956283a1d58ebe1ff1.tar.gz | |
perf_hooks: remove less useful bootstrap marks
While `perf_hooks` is still in experimental, remove less useful
bootstrap milestones.
PR-URL: https://github.com/nodejs/node/pull/21247
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Tiancheng "Timothy" Gu <timothygu99@gmail.com>
Diffstat (limited to 'doc/api/perf_hooks.md')
| -rw-r--r-- | doc/api/perf_hooks.md | 78 |
1 files changed, 0 insertions, 78 deletions
diff --git a/doc/api/perf_hooks.md b/doc/api/perf_hooks.md index a8c6bcf737..f16a217bbe 100644 --- a/doc/api/perf_hooks.md +++ b/doc/api/perf_hooks.md @@ -219,26 +219,6 @@ The high resolution millisecond timestamp at which the Node.js process completed bootstrapping. If bootstrapping has not yet finished, the property has the value of -1. -### performanceNodeTiming.clusterSetupEnd -<!-- YAML -added: v8.5.0 ---> - -* {number} - -The high resolution millisecond timestamp at which cluster processing ended. If -cluster processing has not yet ended, the property has the value of -1. - -### performanceNodeTiming.clusterSetupStart -<!-- YAML -added: v8.5.0 ---> - -* {number} - -The high resolution millisecond timestamp at which cluster processing started. -If cluster processing has not yet started, the property has the value of -1. - ### performanceNodeTiming.loopExit <!-- YAML added: v8.5.0 @@ -261,24 +241,6 @@ The high resolution millisecond timestamp at which the Node.js event loop started. If the event loop has not yet started (e.g., in the first tick of the main script), the property has the value of -1. -### performanceNodeTiming.moduleLoadEnd -<!-- YAML -added: v8.5.0 ---> - -* {number} - -The high resolution millisecond timestamp at which main module load ended. - -### performanceNodeTiming.moduleLoadStart -<!-- YAML -added: v8.5.0 ---> - -* {number} - -The high resolution millisecond timestamp at which main module load started. - ### performanceNodeTiming.nodeStart <!-- YAML added: v8.5.0 @@ -289,46 +251,6 @@ added: v8.5.0 The high resolution millisecond timestamp at which the Node.js process was initialized. -### performanceNodeTiming.preloadModuleLoadEnd -<!-- YAML -added: v8.5.0 ---> - -* {number} - -The high resolution millisecond timestamp at which preload module load ended. - -### performanceNodeTiming.preloadModuleLoadStart -<!-- YAML -added: v8.5.0 ---> - -* {number} - -The high resolution millisecond timestamp at which preload module load started. - -### performanceNodeTiming.thirdPartyMainEnd -<!-- YAML -added: v8.5.0 ---> - -* {number} - -The high resolution millisecond timestamp at which third\_party\_main -processing ended. If third\_party\_main processing has not yet ended, the -property has the value of -1. - -### performanceNodeTiming.thirdPartyMainStart -<!-- YAML -added: v8.5.0 ---> - -* {number} - -The high resolution millisecond timestamp at which third\_party\_main -processing started. If third\_party\_main processing has not yet started, the -property has the value of -1. - ### performanceNodeTiming.v8Start <!-- YAML added: v8.5.0 |