Re: [HighResTime] Web Worker support

Our use cases require comparing times from workers with their parent page
context, but if that's possible to do with a delta of load time of the
different contexts (performance.timing.navigationStart in the page and
performance.whatever in the worker) instead of having now() values line up
that's fine.


On Tue, Sep 10, 2013 at 4:09 PM, Jatinder Mann <jmann@microsoft.com> wrote:

>  Let’s discuss performance.originTime in this week’s call. We had raised
> the idea of possibly defining the origin time, so that time values obtained
> from a shared worker context could be compared with a dedicated worker or
> the top level browsing context. Not sure how common it will be to compare
> time values from different contexts, but it’s worth discussing.****
>
> ** **
>
> Thanks,****
>
> Jatinder****
>
> ** **
>
> *From:* James Simonsen [mailto:simonjam@chromium.org]
> *Sent:* Wednesday, September 4, 2013 1:35 PM
> *To:* public-web-perf
>
> *Subject:* Re: [HighResTime] Web Worker support****
>
> ** **
>
> On Tue, May 14, 2013 at 11:20 AM, James Simonsen <simonjam@chromium.org>
> wrote:****
>
>  Sorry for being late getting back to this thread...****
>
> ** **
>
> On Thu, Apr 18, 2013 at 10:44 AM, Jatinder Mann <jmann@microsoft.com>
> wrote:****
>
>  Ben,****
>
>  ****
>
> If you’re just looking at deltas, differences between two time values, the
> origin shouldn’t matter. Is there a case where deltas wouldn’t be good
> enough and you would want the absolute numbers?****
>
>  ****
>
> If we were are to provide the origin time as a separate value (e.g.,
> performance.originTime), it would need to be in the same sub-millisecond
> resolution in order to be comparable with other DOMHighResTimeStamps; the
> spec currently suggests one thousandth of a millisecond. Double precision
> may be able to support that for milliseconds since Unix epoch.****
>
>  ** **
>
> I don't fully understand the originTime. Is this effectively a global
> monotonic clock across all processes (workers and tabs)?****
>
>  ** **
>
> Ping? Are we going to do anything about this?****
>
> ** **
>
> James ****
>