@@ -181,7 +181,8 @@ added: v8.5.0
181181
182182* Returns: {number}
183183
184- Returns the current high resolution millisecond timestamp.
184+ Returns the current high resolution millisecond timestamp, where 0 represents
185+ the start of the current ` node ` process.
185186
186187### performance.timeOrigin
187188<!-- YAML
@@ -190,8 +191,8 @@ added: v8.5.0
190191
191192* {number}
192193
193- The [ ` timeOrigin ` ] [ ] specifies the high resolution millisecond timestamp from
194- which all performance metric durations are measured.
194+ The [ ` timeOrigin ` ] [ ] specifies the high resolution millisecond timestamp at
195+ which the current ` node ` process began, measured in Unix time .
195196
196197### performance.timerify(fn)
197198<!-- YAML
@@ -302,7 +303,8 @@ added: v8.5.0
302303* {number}
303304
304305The high resolution millisecond timestamp at which the Node.js process
305- completed bootstrap.
306+ completed bootstrapping. If bootstrapping has not yet finished, the property
307+ has the value of -1.
306308
307309### performanceNodeTiming.clusterSetupEnd
308310<!-- YAML
@@ -311,7 +313,8 @@ added: v8.5.0
311313
312314* {number}
313315
314- The high resolution millisecond timestamp at which cluster processing ended.
316+ The high resolution millisecond timestamp at which cluster processing ended. If
317+ cluster processing has not yet ended, the property has the value of -1.
315318
316319### performanceNodeTiming.clusterSetupStart
317320<!-- YAML
@@ -321,6 +324,7 @@ added: v8.5.0
321324* {number}
322325
323326The high resolution millisecond timestamp at which cluster processing started.
327+ If cluster processing has not yet started, the property has the value of -1.
324328
325329### performanceNodeTiming.loopExit
326330<!-- YAML
@@ -330,7 +334,8 @@ added: v8.5.0
330334* {number}
331335
332336The high resolution millisecond timestamp at which the Node.js event loop
333- exited.
337+ exited. If the event loop has not yet exited, the property has the value of -1.
338+ It can only have a value of not -1 in a handler of the [ ` 'exit' ` ] [ ] event.
334339
335340### performanceNodeTiming.loopStart
336341<!-- YAML
@@ -340,7 +345,8 @@ added: v8.5.0
340345* {number}
341346
342347The high resolution millisecond timestamp at which the Node.js event loop
343- started.
348+ started. If the event loop has not yet started (e.g., in the first tick of the
349+ main script), the property has the value of -1.
344350
345351### performanceNodeTiming.moduleLoadEnd
346352<!-- YAML
@@ -395,8 +401,9 @@ added: v8.5.0
395401
396402* {number}
397403
398- The high resolution millisecond timestamp at which third_party_main processing
399- ended.
404+ The high resolution millisecond timestamp at which third\_ party\_ main
405+ processing ended. If third\_ party\_ main processing has not yet ended, the
406+ property has the value of -1.
400407
401408### performanceNodeTiming.thirdPartyMainStart
402409<!-- YAML
@@ -405,8 +412,9 @@ added: v8.5.0
405412
406413* {number}
407414
408- The high resolution millisecond timestamp at which third_party_main processing
409- started.
415+ The high resolution millisecond timestamp at which third\_ party\_ main
416+ processing started. If third\_ party\_ main processing has not yet started, the
417+ property has the value of -1.
410418
411419### performanceNodeTiming.v8Start
412420<!-- YAML
@@ -642,6 +650,7 @@ obs.observe({ entryTypes: ['function'], buffered: true });
642650require (' some-module' );
643651```
644652
653+ [ `'exit'` ] : process.html#process_event_exit
645654[ `timeOrigin` ] : https://w3c.github.io/hr-time/#dom-performance-timeorigin
646655[ Async Hooks ] : async_hooks.html
647656[ W3C Performance Timeline ] : https://w3c.github.io/performance-timeline/
0 commit comments