New issue
Advanced search Search tips

Issue 893760 link

Starred by 1 user
Status: Untriaged
Owner:
sonnyrao@chromium.org
Cc:
vovoy@chromium.org
chinglinyu@chromium.org
semenzato@chromium.org
conradlo@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

report tab discard/app kill and OOM kill metrics over a one day interval

Project Member Reported by sonnyrao@chromium.org, Oct 9 
Right now we have UMA metrics that are reporting tab discards, app kills and kernel OOM kills per-session and the histograms show these metrics in a cumulative fashion.  

This can make it slightly confusing to determine how many users experienced one or more events, and the per-session aspect makes it hard to determine how often the users are experiencing these events.

Instead, I'm proposing that we report a Daily count of these events per user.  This will make it more clear how often our users are experiencing these events.

Comment 1 by sonnyrao@chromium.org, Oct 9 

We could do this from metrics daemon or from memd.  Given that we're also trying to add some other metrics to memd like time intervals from signal to discard in memd -- see crbug.com/852906 -- it would make sense to consolidate there.

Comment 2 by sonnyrao@chromium.org, Jan 2 

One more thing we want to collect is time from signal to discard.  Currently we're polling on a one second interval and we sometimes see almost a second of latency between the signal and discard in the memd logs.
►

Sign in to add a comment