Hi,
as you have correctly observed, the timeline plot only takes those
callbacks into account that are done in a VMState scope: VMState changes to
and from EXTERNAL are logged. Fast API calls, i.e. jitted ones, are
therefore not logged. That is, unless you specify --log-timer-events, which
causes
On Tue, Jun 11, 2013 at 2:38 AM, Kentaro Hara wrote:
>> Also, I'm a bit surprised at the way the v8 DOM callbacks end up in
>> the profile: those methods are usually trivial, with the real work
>> being somewhere deep in the core of Blink. Is it expected that only
>> the v8 entry point into Blink
On Tue, Jun 11, 2013 at 7:24 AM, Adam Klein wrote:
> I'm trying to profile the v8 execution of a web app using Chromium's
> content_shell with some success. But I'm also getting some odd
> results. I'm using a commandline like:
>
> content_shell --no-sandbox --js-flags='--prof --noprof-lazy
> --lo
>
> Also, I'm a bit surprised at the way the v8 DOM callbacks end up in
> the profile: those methods are usually trivial, with the real work
> being somewhere deep in the core of Blink. Is it expected that only
> the v8 entry point into Blink shows up when using the profiling tool?
I've played ar
+kentaro for some profiling insights
On Tue, Jun 11, 2013 at 7:24 AM, Adam Klein wrote:
> I'm trying to profile the v8 execution of a web app using Chromium's
> content_shell with some success. But I'm also getting some odd
> results. I'm using a commandline like:
>
> content_shell --no-sandbox
I'm trying to profile the v8 execution of a web app using Chromium's
content_shell with some success. But I'm also getting some odd
results. I'm using a commandline like:
content_shell --no-sandbox --js-flags='--prof --noprof-lazy
--log-timer-events' http://localhost:8000/mypage
And then processi
