Re: [v8-users] performance.now resolution

2017-02-03 Thread Brian Hicks
Thanks Jakob1 I found out after I sent the original message that performance.now is constrained to 5µs resolution anyway for security reasons, but it's good to know about the implementation. -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users ---

Re: [v8-users] performance.now resolution

2017-02-03 Thread Jakob Kummerow
Some sort of rounding error, yes. The internal representation (before converting the value to float) is microseconds. Actual precision depends on the operating system, as the comment in time.h says: // Returns a platform-dependent high-resolution tick count. Implementation > // is hardware