Issue 2337023004: Do not add TTI if interactive state was not reached

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Issue 2337023004: Do not add TTI if interactive state was not reached

Created:
4 years, 3 months ago by dproy-google

Modified:
4 years, 3 months ago

Reviewers:

CC:
catapult-reviews_chromium.org, tracing-review_chromium.org

Target Ref:
refs/heads/master

Project:
catapult

Visibility:
Public.

More Reviews

Description

Do not add TTI if interactive state was not reached Assume there are two navigations happening at times N1 and N2, and they have corresponding FMPs achieved at times P1 and P2. Currently, if the first navigation achieves FMP but not interactive state (i.e. navigation N2 happens too soon), while the second navigation does achieve interactive state (say at time T2), then we report two TTI values: N1 -> T2, and N2 -> T2. This CL changes the behavior so that we only report N2 -> T2. It does this by looking out for navigationStart events while trying to find the window of inactivity, and if found, aborts the search for TTI. BUG=chromium:640957

Patch Set 1 #

Created: 4 years, 3 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+8 lines, -1 line)			Patch
	M	tracing/tracing/metrics/system_health/loading_metric.html	View		2 chunks	+8 lines, -1 line	0 comments	Download