@@ -181,7 +181,8 @@ added: v8.5.0
181
181
182
182
* Returns: {number}
183
183
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.
185
186
186
187
### performance.timeOrigin
187
188
<!-- YAML
@@ -190,8 +191,8 @@ added: v8.5.0
190
191
191
192
* {number}
192
193
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 .
195
196
196
197
### performance.timerify(fn)
197
198
<!-- YAML
@@ -302,7 +303,8 @@ added: v8.5.0
302
303
* {number}
303
304
304
305
The 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.
306
308
307
309
### performanceNodeTiming.clusterSetupEnd
308
310
<!-- YAML
@@ -311,7 +313,8 @@ added: v8.5.0
311
313
312
314
* {number}
313
315
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.
315
318
316
319
### performanceNodeTiming.clusterSetupStart
317
320
<!-- YAML
@@ -321,6 +324,7 @@ added: v8.5.0
321
324
* {number}
322
325
323
326
The high resolution millisecond timestamp at which cluster processing started.
327
+ If cluster processing has not yet started, the property has the value of -1.
324
328
325
329
### performanceNodeTiming.loopExit
326
330
<!-- YAML
@@ -330,7 +334,8 @@ added: v8.5.0
330
334
* {number}
331
335
332
336
The 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.
334
339
335
340
### performanceNodeTiming.loopStart
336
341
<!-- YAML
@@ -340,7 +345,8 @@ added: v8.5.0
340
345
* {number}
341
346
342
347
The 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.
344
350
345
351
### performanceNodeTiming.moduleLoadEnd
346
352
<!-- YAML
@@ -395,8 +401,9 @@ added: v8.5.0
395
401
396
402
* {number}
397
403
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.
400
407
401
408
### performanceNodeTiming.thirdPartyMainStart
402
409
<!-- YAML
@@ -405,8 +412,9 @@ added: v8.5.0
405
412
406
413
* {number}
407
414
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.
410
418
411
419
### performanceNodeTiming.v8Start
412
420
<!-- YAML
@@ -642,6 +650,7 @@ obs.observe({ entryTypes: ['function'], buffered: true });
642
650
require (' some-module' );
643
651
```
644
652
653
+ [ `'exit'` ] : process.html#process_event_exit
645
654
[ `timeOrigin` ] : https://w3c.github.io/hr-time/#dom-performance-timeorigin
646
655
[ Async Hooks ] : async_hooks.html
647
656
[ W3C Performance Timeline ] : https://w3c.github.io/performance-timeline/
0 commit comments