Difference in scripting time in devtools and Chrome
soulgalore opened this issue · comments
Hi Paul,
I've been trying out the devtools timeline (great work, it so nice to not parse the log) and it seems like scripting time is always low.
If I drag and drop the tracelog into Chrome 64 I get this:
And from devtools-timeline-model (model.bottomUpGroupBy('Category').children):
{ rendering: 1851.997999727726,
scripting: 303.46600019931793,
loading: 120.90799987316132,
painting: 51.13799995183945 }
Here's the trace I used: https://gist.github.com/soulgalore/1946f6d3ed8da35c904e14c08985e172
Seen the same thing on other pages too. Could the reason be that it depends on an old chrome-devtools-frontend?
Best
Peter
Hi. Can you share the code for getting the timings info from model.bottomUpGroupBy('Category').children?