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

Issue 809766 link

Starred by 0 users

Issue metadata

Status: Duplicate
Owner:
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Improve Metric: InstantTethering.Performance.AdvertisementToConnectionDuration

Project Member Reported by khorimoto@chromium.org, Feb 6 2018

Issue description

https://uma.googleplex.com/p/chrome/histograms?endDate=latest&dayCount=7&histograms=InstantTethering.Performance.AdvertisementToConnectionDuration&fixupData=true&uniqueUsers=true&showMax=true&filters=platform%2Ceq%2CC%2Cchannel%2Cone_of%2C4%7C3%7C2%7C1%2Cisofficial%2Ceq%2CTrue&implicitFilters=isofficial

The bucket with the most metrics is the top bucket, which ranges from 10,000ms to 2,147,483,647ms. Because this bucket is so large that it spans 5 orders of magnitude, we do not have a clear idea of what is going on with the metric.

I believe Ryan originally chose 10s to be the maximum bucket because we have a 10s timeout. However, that timeout is the time between starting to advertise to a device and receiving a scan result from that same device. The metric, however, is logged after receiving a scan result *and* creating a GATT connection to the device, which means that real connections can often take >10s.
 
Mergedinto: 785363
Status: Duplicate (was: Assigned)
This issue has since been fixed, it was tracked by (and is a dupe of) crbug.com/785363.

Sign in to add a comment