Page MenuHomePhabricator

Test out WebPageTest trace parsing lib
Closed, ResolvedPublic

Description

The https://github.com/paulirish/devtools-timeline-model that has a couple of bugs (reporting too low scripting time and unclear detailed scripting report). I've reported it upstream and I can ping Paul Irish in a couple of days (Lighthouse uses the same library internally so they also have the same problem).

We can try out the trace parser that WebPageTest uses, it is Open Source and broken out of WebPageTest https://github.com/WPO-Foundation/trace-parser

It will need some more work: The parser generates a new JSON file that we need to parse again and map each event against each category (scripting/rendering etc) but we already do that in the WebPageTest wrapper so we can reuse that.

Event Timeline

Peter triaged this task as Medium priority.

Made a quick hack to compare numbers. In devtools the same trace log (testing the Obama page) looks like this:

Screen Shot 2018-01-29 at 10.45.40 AM.png (572×310 px, 42 KB)

Using the devtools-timeline project:
Loading: 74
Scripting: 295
Rendering: 2172
Painting: 35

Then the trace-parser gives us:
Loading: 69
Scripting: 511
Rendering (Layout): 2063
Painting: 145

The trace parser looks better, the scripting is just too low in the devtools-timeline.

I've implemented the trace-parser and hope to push it to the server tomorrow.

This is runs on the servers now in a special made Docker container.