Benjamin Smedberg Assignee
	Description • 7 years ago

While we wait for the mission control project, we want a custom job to report on some of the quantum release criteria. This includes the following:

% of sessions that experience a nonzero GHOST_WINDOWS measurement
% of weekly users who experience chrome GC or CC pauses >150ms
% of weekly users who experience content GC or CC pauses >2500ms
MTBF of {chrome,content} input latency greater than {250ms,2500ms}

	Frank Bertsch [:frank]
	Comment 1 • 7 years ago

I'm covering the creation of these datasets in a metabug.

	Frank Bertsch [:frank]
	Comment 2 • 7 years ago

Sounds like this is slightly different and just meant for temporary measures. Reopening.

	Benjamin Smedberg Assignee
	Comment 3 • 7 years ago

This is now running daily and uploading to https://s3-us-west-2.amazonaws.com/telemetry-public-analysis-2/bsmedberg/daily-latency-metrics/20170609.json 

This is Windows-only and divides the data up into two categories: quantum-ready is the user-base we care about and should probably report on for quantum release criteria. People can be excluded from that for having an old-style theme, having a non-webextension, or for not running e10s.

Harald, please confirm that this is what you need for reporting.

	:Harald Kirschner :digitarald
	Comment 4 • 7 years ago

If I am not mistaken this has MTBF for input latency but lacks % of users (weekly) affected.

	:Harald Kirschner :digitarald
	Comment 5 • 7 years ago

Just having a week of entries doesn't really tell a story of progress Quantum has made in the past months. Can we backfill more dates to make it easier for engineers to track progress since Apr 1st? Weekly should be enough.

	Benjamin Smedberg Assignee
	Comment 6 • 7 years ago

Backfill is expensive for this dataset and many of the measures were only completed properly in the last month, so we're not going to backfill.

As noted on slack, I added the % of users affected for input latency.