W3C home > Mailing lists > Public > public-web-perf@w3.org > August 2016

Re: Long Tasks Notifications API

From: Ben Maurer <ben.maurer@gmail.com>
Date: Fri, 5 Aug 2016 16:04:59 -0700
Message-ID: <CABgOVa+0SQVUQoj6HFqyMndbPVQsvkK41n=u+mftPLmefVDGHw@mail.gmail.com>
To: Shubhie Panicker <panicker@google.com>
Cc: public-web-perf <public-web-perf@w3.org>, Ilya Grigorik <igrigorik@google.com>, Nat Duca <nduca@google.com>
On Fri, Aug 5, 2016 at 3:22 PM, Shubhie Panicker <panicker@google.com>
wrote:

> - Re: callback wrappers
> As seen in the common script execution patterns
> <https://docs.google.com/document/d/1UCJHjDB5ttYdDH3B9xggev10euRV3wsRR3jCoQi9AwM/edit>
> - there’s a couple different frequent patterns.
> For v8.run the URL is available; for direct entry into callFunction we
> have the obfuscated / minified function name string -- this is similar to
> what you’d see in Devtools timeline with JS Profile. (You’d deobfuscate
> using your own pipeline)
> From a quick look at Devtools Js Profile on facebook -- I do see a
> frequently occurring entry point for scripts - this is probably your
> wrapper.
> We should probably discuss your specific wrapper situation offline, as I
> don't see this as a very common pattern on other top sites.
>

Yeah, that's very likely our wrapper. Happy to discuss potential solutions
offline. A bit surprised this pattern hasn't shown up in other sites.



> - Re: extensions
> We *may* be able to indicate something generic here. Prior investigation
> <https://codereview.chromium.org/1615523002/> indicates that it's very
> difficult to properly account for scripts spawned by extensions.
>

I see. With your current implementation how would time spent in extensions
show up?

-b
Received on Friday, 5 August 2016 23:05:28 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 18 September 2016 16:33:38 UTC