Performance/Status Meetings/2007-June-06: Difference between revisions

Jump to navigation Jump to search
note on timing
(note on timing)
Line 52: Line 52:


In general, I _think_ that anything that's using JS Date.now() directly is good for 1ms precision (which means that tasks of under 100ms are hard to time to 1% accuracy).  Anything using timeouts (I seem to recall Tp does this?) will get noise in it due to PR_IntervalNow; on Windows this might be a lot of noise.  Ts uses the Perl timing, which should be ok.
In general, I _think_ that anything that's using JS Date.now() directly is good for 1ms precision (which means that tasks of under 100ms are hard to time to 1% accuracy).  Anything using timeouts (I seem to recall Tp does this?) will get noise in it due to PR_IntervalNow; on Windows this might be a lot of noise.  Ts uses the Perl timing, which should be ok.
:JS timing is actually worse than 1ms on Mac - granularity is in 16 ms ticks, easily visible if you graph timings of short loops. gettimeofday() on Mac has a 1-microsecond granularity though. -Stan


== Other Information ==
== Other Information ==
20

edits

Navigation menu