Open Bug 1601401 Opened 3 months ago Updated 3 months ago

Odd results testing ./mach browsertime with fission

Categories

(Core :: Networking, defect, P3)

defect

Tracking

()

Fission Milestone M6

People

(Reporter: jesup, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [fission][necko-triaged])

When testing browsertime with fission (via --firefox.preference fission.autostart:true), you get odd results. BackEndTime is always negative; most other measurements are better than non-fission (though I don't see that in hand testing), but visualMetrics shows considerable regression.

I see this with CNN (including visual metrics), and Netflix (I didn't have them working for this test).

Not sure why; perhaps the negative BackEndTime is a clue to what goes wrong here.

Blocking the main browsertime meta since I assume it affects CI and local; feel free to move to blocking local and (I assume) CI use.

May be related to bug 1417308

From a run:
[2019-12-05 07:52:27] INFO: https://www.cnn.com/ BackEndTime: -337 DomInteractiveTime: 540 DomContentLoadedTime: 552 FirstPaint: 535 PageLoadTime: 1951
[2019-12-05 07:52:27] INFO: VisualMetrics FirstVisualChange: 2320 SpeedIndex: 3662 PerceptualSpeedIndex: 4964 ContentfulSpeedIndex: 3422 VisualComplete85: 5720 LastVisualChange: 6480

and the json recorded by browsertime from our APIs:
"navigationTiming": {
"connectStart": -373,
"domComplete": 1951,
"domContentLoadedEventEnd": 643,
"domContentLoadedEventStart": 552,
"domInteractive": 540,
"domainLookupEnd": -373,
"domainLookupStart": -394,
"duration": 2291,
"fetchStart": -402,
"loadEventEnd": 2291,
"loadEventStart": 1951,
"redirectEnd": 0,
"redirectStart": 0,
"requestStart": -349,
"responseEnd": -311,
"responseStart": -337,
"secureConnectionStart": -365,
"startTime": 0,
"unloadEventEnd": 0,
"unloadEventStart": 0,
"workerStart": 0
},
"pageTimings": {
"backEndTime": -337,
"domContentLoadedTime": 552,
"domInteractiveTime": 540,
"domainLookupTime": 21,
"frontEndTime": 2262,
"pageDownloadTime": 26,
"pageLoadTime": 1951,
"redirectionTime": 0,
"serverConnectionTime": 24,
"serverResponseTime": 38
},

Component: Performance → Networking
Product: Testing → Core
See Also: → 1417308
Whiteboard: [fission]
Version: Version 3 → Trunk

Tracking for Fission Nightly (M6)

Fission Milestone: --- → M6
Priority: -- → P3
Whiteboard: [fission] → [fission][necko-triaged]
You need to log in before you can comment on or make changes to this bug.