New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 684046 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Mar 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Split FirstWebContents startup stats by workload type

Project Member Reported by gab@chromium.org, Jan 23 2017

Issue description

Let's refine Startup.FirstWebContents.* by workload type, I'm thinking of {.SingleNtp, .SingleNonNtp, .MultipleTabs}.

Isolating .SingleNtp will help minimize the problem IMO.
 

Comment 1 by gab@chromium.org, Jan 23 2017

Decided to only tack it on to Startup.FirstWebContents.MainNavigationStart and as such to not bother about NTP since it shouldn't matter.

Startup.FirstWebContents.MainNavigationStart.SingleTab should then be our ground truth for noise-free startups.

Comment 3 by gab@chromium.org, Mar 20 2017

Cc: rkaplow@chromium.org asvitk...@chromium.org rsch...@chromium.org
Status: Fixed (was: Started)
+CC occasional startup performance trackers FYI.

Startup.FirstWebContents.MainNavigationStart.SingleTab((.Cold|LukeWarm|Warm)Startup) is now on M58 Beta. The difference between .SingleTab and .Multitabs isn't as large as I'd expected but .SingleTab will still be a better metric for "browser startup" that further reduces the noise.

https://uma.googleplex.com/p/chrome/histograms/?endDate=20170319&dayCount=3&histograms=Startup.FirstWebContents.MainNavigationStart.MultiTabs.ColdStartup%2CStartup.FirstWebContents.MainNavigationStart.MultiTabs.WarmStartup%2CStartup.FirstWebContents.MainNavigationStart.SingleTab.ColdStartup%2CStartup.FirstWebContents.MainNavigationStart.SingleTab.WarmStartup&fixupData=true&showMax=true&filters=channel%2Ceq%2C3%2Cplatform%2Ceq%2CW%2Cisofficial%2Ceq%2CTrue&implicitFilters=isofficial

Sign in to add a comment