Skip to content
This repository has been archived by the owner on Feb 29, 2020. It is now read-only.

fix(telemetry): #3118 workaround 500s apparent topsites_first_paint_ts #3128

Merged
merged 1 commit into from Aug 10, 2017

Conversation

dmose
Copy link
Member

@dmose dmose commented Aug 10, 2017

Fix #3118. r?Mardak This should be the exact fix we already discussed.

@@ -266,6 +265,13 @@ this.TelemetryFeed = class TelemetryFeed {
// get blows up.
let session = this.sessions.get(port);

// Partial workaround for #3118; avoids the worst incorrect associations of
// times with browsers, and should result in no longer having apparent load
// times of 500,000 ms. Better fix for more cases forthcoming.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The 500sec comment doesn't really make any sense by itself. Probably better to just say to associate the load trigger with the visibility event as the user is most likely associating the trigger to the tab just shown. Could maybe note that this is to not associate with a preloaded browser as those don't get the event until shown.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch, the 500sec was pretty context-free. :-)

@coveralls
Copy link

Coverage Status

Coverage remained the same at 86.407% when pulling c03f842 on dmose:improve-loadtime-correctness into 6864331 on mozilla:master.

assert.calledOnce(instance.setLoadTriggerInfo);
assert.calledWithExactly(instance.setLoadTriggerInfo, "port123");
assert.include(instance.sessions.get("port123").perf, data);
});
Copy link
Member

@Mardak Mardak Aug 10, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A negative test would be good sanity check. I.e., non-visibility_event_rcvd_ts doesn't call setLoadTriggerInfo

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea; done.

@dmose dmose force-pushed the improve-loadtime-correctness branch from c03f842 to 80565ac Compare August 10, 2017 16:56
@coveralls
Copy link

Coverage Status

Coverage remained the same at 86.407% when pulling 80565ac on dmose:improve-loadtime-correctness into fd867e8 on mozilla:master.

@dmose dmose merged commit 84494fe into mozilla:master Aug 10, 2017
@dmose dmose deleted the improve-loadtime-correctness branch August 10, 2017 17:02
@as-pine-proxy
Copy link
Collaborator

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Better handle session start load trigger information with preloaded
4 participants