performance-now

WebJar for performance-now

License

License

MIT
Categories

Categories

ORM Data
GroupId

GroupId

org.webjars.npm
ArtifactId

ArtifactId

performance-now
Last Version

Last Version

2.1.0
Release Date

Release Date

Type

Type

jar
Description

Description

performance-now
WebJar for performance-now
Project URL

Project URL

http://webjars.org
Source Code Management

Source Code Management

https://github.com/braveg1rl/performance-now

Download performance-now

How to add to project

<!-- https://jarcasting.com/artifacts/org.webjars.npm/performance-now/ -->
<dependency>
    <groupId>org.webjars.npm</groupId>
    <artifactId>performance-now</artifactId>
    <version>2.1.0</version>
</dependency>
// https://jarcasting.com/artifacts/org.webjars.npm/performance-now/
implementation 'org.webjars.npm:performance-now:2.1.0'
// https://jarcasting.com/artifacts/org.webjars.npm/performance-now/
implementation ("org.webjars.npm:performance-now:2.1.0")
'org.webjars.npm:performance-now:jar:2.1.0'
<dependency org="org.webjars.npm" name="performance-now" rev="2.1.0">
  <artifact name="performance-now" type="jar" />
</dependency>
@Grapes(
@Grab(group='org.webjars.npm', module='performance-now', version='2.1.0')
)
libraryDependencies += "org.webjars.npm" % "performance-now" % "2.1.0"
[org.webjars.npm/performance-now "2.1.0"]

Dependencies

There are no dependencies for this project. It is a standalone project that does not depend on any other jars.

Project Modules

There are no modules declared in this project.

performance-now Build Status Dependency Status

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 milliseconds, but with sub-millisecond precision. This module offers the same function based on the Node.js native process.hrtime function.

Using process.hrtime means that the reported time will be monotonically increasing, and not subject to clock-drift.

According to the High Resolution Time specification, the number of milliseconds reported by performance.now should be relative to the value of performance.timing.navigationStart.

In the current version of the module (2.0) the reported time is relative to the time the current Node process has started (inferred from process.uptime()).

Version 1.0 reported a different time. The reported time was relative to the time the module was loaded (i.e. the time it was first required). If you need this functionality, version 1.0 is still available on NPM.

Example usage

var now = require("performance-now")
var start = now()
var end = now()
console.log(start.toFixed(3)) // the number of milliseconds the current node process is running
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.

License

performance-now is released under the MIT License. Copyright (c) 2017 Braveg1rl

Versions

Version
2.1.0
0.2.0
0.1.3