Re: Exposing high-res time in workers

A common use case for these things is to build up a timeline for
performance analysis in order to understand how well one's threading
strategy is working out. E.g. a js version of
http://dev.chromium.org/developers/how-tos/trace-event-profiling-tool. For
such scenario, sharing the timebase of the owning page seems critical.


On Mon, May 5, 2014 at 12:03 PM, Jonas Sicking <jonas@sicking.cc> wrote:

> I think we'd also need to define what reference point to use,
> especially for dedicated workers. Do we make 0 refer to when the
> worker first started, or do we make a dedicated worker use the same
> reference point as its owning page.
>
> / Jonas
>
> On Mon, May 5, 2014 at 8:46 AM, Domenic Denicola
> <domenic@domenicdenicola.com> wrote:
> > Hi all,
> >
> > I am sitting in an EmpireJS talk by Andrew Petersen, CC'ed, who pointed
> out
> > on-stage that one of the features he misses inside web workers is
> > high-resolution time. If there's a desire for use-cases, I hope he can
> chime
> > in.
> >
> > From a spec perspective, this seems like a pretty easy tweak: I believe
> the
> > WebIDL these days is [Exposed=Window,Worker]. I assume from an
> > implementation perspective it is not much harder either.
> >
> > What does the working group think?
>
>