From dd83b5f2ac3a9684044b4aa5ad0b3832ea63694b Mon Sep 17 00:00:00 2001 From: Sam Roberts Date: Wed, 27 Sep 2017 12:28:21 -0700 Subject: [PATCH] perf_hooks: remove docs for unimplemented API The node frame (aka loop) timing API did not land, it depends on https://github.com/libuv/libuv/pull/1489 which is still a WIP. See: https://github.com/nodejs/node/pull/14680#discussion_r140605664 PR-URL: https://github.com/nodejs/node/pull/15641 Reviewed-By: Colin Ihrig Reviewed-By: Timothy Gu Reviewed-By: James M Snell Reviewed-By: Luigi Pinca Reviewed-By: Jeremiah Senkpiel Reviewed-By: Ruben Bridgewater --- doc/api/perf_hooks.md | 41 ----------------------------------------- 1 file changed, 41 deletions(-) diff --git a/doc/api/perf_hooks.md b/doc/api/perf_hooks.md index c6705e90096d31..09582cea80bb0a 100644 --- a/doc/api/perf_hooks.md +++ b/doc/api/perf_hooks.md @@ -135,16 +135,6 @@ the Performance Timeline or any of the timestamp properties provided by the `PerformanceNodeTiming` class. If the named `endMark` does not exist, an error will be thrown. -### performance.nodeFrame - - -* {PerformanceFrame} - -An instance of the `PerformanceFrame` class that provides performance metrics -for the event loop. - ### performance.nodeTiming - -Provides timing details for the Node.js event loop. - -### performanceNodeFrame.frameCheck - -The high resolution timestamp when `uv_check_t` processing occurred on the -current loop. - -### performanceNodeFrame.frameCount - -The total number of event loop iterations (iterated when `uv_idle_t` -processing occurrs). - -### performanceNodeFrame.frameIdle - -The high resolution timestamp when `uv_idle_t` processing occurred on the -current loop. - -### performanceNodeFrame.framesPerSecond - -The number of event loop iterations per second. - -### performanceNodeFrame.framePrepare - -The high resolution timestamp when `uv_prepare_t` processing occurred on the -current loop. - ## Class: PerformanceNodeTiming extends PerformanceEntry