That doesn't change the fact that benchmarks do not provide reliable information when they don't run long enough.
On Thu, Feb 21, 2013 at 12:11 AM, Dave Pacheco <[email protected]> wrote: > On Fri, Feb 1, 2013 at 12:57 AM, Jakob Kummerow <[email protected]>wrote: > >> "Date.now()" or "new Date()" are commonly used for JS benchmarking. They >> should be reliable, but they obviously have 1ms granularity, so I'd try to >> make sure that my benchmark runs for 1000 ms or so to get good results. >> > > > Node.js also provides process.hrtime() for high-resolution, non-drifting > timestamps suitable for measuring performance. > > -- Dave > > -- > -- > v8-users mailing list > [email protected] > http://groups.google.com/group/v8-users > --- > You received this message because you are subscribed to the Google Groups > "v8-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
