performance-now
Advanced tools
Package description
The performance-now npm package provides a high-resolution timestamp, similar to what you would get from performance.now() in a web browser. This is particularly useful for accurately measuring execution times in Node.js applications, where such precision is necessary for performance analysis and optimization.
High-resolution timing
This feature allows you to measure the time it takes to execute operations with high precision. The code sample demonstrates how to use performance-now to calculate the execution time of some operations in milliseconds.
const now = require('performance-now');
let start = now();
// Some time-consuming operations
let end = now();
console.log(`Execution time: ${end - start} milliseconds`);Provides a shim for Date.now(). While it offers functionality to get the current timestamp, it does not offer the high-resolution timing that performance-now does, making it less suitable for precise performance measurements.
This package is a polyfill for process.hrtime. It offers high-resolution time measurements similar to performance-now but is specifically designed to mimic Node.js's process.hrtime() method, making it more suitable for applications that rely on process.hrtime() for compatibility reasons.
Offers high-resolution timestamps in nanoseconds. While it provides similar functionality to performance-now in terms of high-resolution timing, nano-time focuses on nanosecond precision, which can be more than what is needed for most performance measurement scenarios.
Readme
Implements a function similar to performance.now (based on process.hrtime).
Modern browsers have a window.performance object with - among others - a now method which gives time in miliseconds, but with sub-milisecond precision. This module offers the same function based on the Node.js native process.hrtime function.
According to the High Resolution Time specification, the number of miliseconds reported by performance.now should be relative to the value of performance.timing.navigationStart. For this module, it's relative to when the time when this module got loaded. Right after requiring this module for the first time, the reported time is expected to have a near-zero value.
Using process.hrtime means that the reported time will be monotonically increasing, and not subject to clock-drift.
var now = require("performance-now")
var start = now()
var end = now()
console.log(start.toFixed(3)) // ~ 0.05 on my system
console.log((start-end).toFixed(3)) // ~ 0.002 on my system
Running the now function two times right after each other yields a time difference of a few microseconds. Given this overhead, I think it's best to assume that the precision of intervals computed with this method is not higher than 10 microseconds, if you don't know the exact overhead on your own system.
The initial structure of this module was generated by Jumpstart, using the Jumpstart Black Coffee template.
performance-now is released under the MIT License.
Copyright (c) 2013 Braveg1rl
FAQs
Implements performance.now (based on process.hrtime).
The npm package performance-now receives a total of 15,476,044 weekly downloads. As such, performance-now popularity was classified as popular.
We found that performance-now demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
This episode of the Risky Biz podcast discusses how the rise of small open source packages and the shift towards individual maintainers makes the ecosystem more vulnerable to supply chain attacks.
Product
Streamline your login process and enhance security by enabling Single Sign-On (SSO) on the Socket platform, now available for all customers on the Enterprise plan, supporting 20+ identity providers.
Security News
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.