Physical Web UMA: Should report the ResolveTime measurement after doing an explicit "refresh" in a separate bucket. |
||
Issue descriptionToday we already track the number of beacons found on launch vs after refresh. But today we only report Resolve times for background vs foreground, without factoring in refresh time. The reason this number is interesting to isolate is because we expect PWS calls which come in quick succession (as expected by refresh), to resolve faster. We would like to remove this special case of foreground resolve calls, since they bring down the average but don't actually represent typical foreground launch use case. Similarly, we may want to split reporting for "Active scan result", e.g. beacons found after the initial launch during active scanning.
,
May 25 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/d1a23ec7b4749dfd29903a16c7680e4bcd54d21a commit d1a23ec7b4749dfd29903a16c7680e4bcd54d21a Author: cco3 <cco3@chromium.org> Date: Wed May 25 23:06:37 2016 Record UMA for Physical Web refresh resolve time Physical Web Service resolve times are expected to differ based on whether we've recently sent out URLs for resolution, so it makes sense to distinguish between refreshes and non-refresh resolutions in our recorded UMA. BUG= 609945 Review-Url: https://codereview.chromium.org/2005313002 Cr-Commit-Position: refs/heads/master@{#396029} [modify] https://crrev.com/d1a23ec7b4749dfd29903a16c7680e4bcd54d21a/chrome/android/java/src/org/chromium/chrome/browser/physicalweb/ListUrlsActivity.java [modify] https://crrev.com/d1a23ec7b4749dfd29903a16c7680e4bcd54d21a/chrome/android/java/src/org/chromium/chrome/browser/physicalweb/PhysicalWebUma.java [modify] https://crrev.com/d1a23ec7b4749dfd29903a16c7680e4bcd54d21a/tools/metrics/histograms/histograms.xml
,
May 25 2016
|
||
►
Sign in to add a comment |
||
Comment 1 by mmo...@chromium.org
, May 6 2016