Very interesting! I never thought about the effect that other applications
might have on JavaScript timers. Thanks for posting that. (BTW, do you
prefer to go by Pops or Hector?)
Here is something that may be useful in conjunction with your program. A
couple of weeks ago when Yehuda was working
Michael,
Excellent piece of javascript code you have there to begin a real
benchment and summary report of all the browsers, machines, OSes
timing related issues.
I didn't study it yet, but just running it on my XP box with IE and
FF, there are different results. I have to see what that means.
Michael,
At first glance, your code is essentially establishling a baseline for
the optimal timing the js user agent because each test is sequentially
synchronized.
There is a clear difference with IE and FF. This is good and allow
us to being proposing, if further required, a consistent
Michael just a quick comment:
On IE, setInterval(0) does not work, so the page skips that test.
What did you see that made it not work?
I just tried it and setInterval(0) worked fine, just like
setTimeout(0) both provided a 15ms resolution.
I did something like this:
var dispatches = [];
4 matches
Mail list logo
