[Webkit-unassigned] [Bug 119761] Replace currentTime() with monotonicallyIncreasingTime() in all possible places
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Tue Aug 13 12:33:07 PDT 2013
https://bugs.webkit.org/show_bug.cgi?id=119761
--- Comment #6 from Arunprasad Rajkumar <arurajku at cisco.com> 2013-08-13 12:32:41 PST ---
(In reply to comment #4)
> (In reply to comment #2)
> > (In reply to comment #1)
> > > What is the goal of this change? Why do we want to do this?
> >
>
> I'm still not sure replacing calls to currentTime() by monotonicallyIncreasingTime() everywhere is such a great idea. Can't those platforms emulate currentTime?
Not just blindly everywhere. I think wall clock time is needed only in some places like jsDateTime, HTTP Resource Caching,..
>Presumably, this is just an optimization, right?
Yes, it is a kind of optimization. The issue is some of the platform wall clock timer's accuracy is about 10ms(what we using), but monotonicallyIncreasingTime's accuracy is < 1ms.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list