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

Issue 821164 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Mar 2018
Cc:
jianli@chromium.org
█ romax@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

Inconsistencies in Offline Prefetch metrics

Project Member Reported by carlosk@chromium.org, Mar 12 2018 
Looking at some UMA metrics for Offline Prefetch there seems to be some inconsistencies among them. Let's report here what we find and then address it:

To start with, I'd expect these two to match:
* Total Count of OfflinePages.AccessEntryPoint.suggested_articles 
* Total Count of OfflinePages.PageAccessInterval.suggested_articles

Comment 1 by romax@chromium.org, Mar 12 2018 

can you please elaborate what's the 'inconsistency'?

For the total count, my naive theory is that since the channels do have a 'catch up' time since clients need to upgrade their Chrome, it's expected for the "PageAccessInterval' (which was added in Jan. 18) to catch up with 'AccessEntryPoint' (which was added in Oct. 17).

However in Canary and Dev, seems the catching up has mostly completed. Beta is on its way and for stable it just started: https://uma.googleplex.com/p/chrome/timeline_v2/?sid=2cec7e626a65f443f6d124b141f9a832.

Comment 2 by carlosk@chromium.org, Mar 12 2018

Status: WontFix (was: Untriaged)
Yes, you are right. I only realized later that PageAccessInterval was only landed in M65 and so it's still ramping up. Closing as it's WAI.
►

Sign in to add a comment