Open
Bug 1245846
Opened 10 years ago
Updated 3 years ago
Regression in 95th percentile CC max times?
Categories
(Core :: General, defect)
Tracking
()
REOPENED
People
(Reporter: smaug, Unassigned)
Details
https://telemetry.mozilla.org/new-pipeline/evo.html#!aggregates=median!75th-percentile!95th-percentile&cumulative=0&end_date=2016-02-03&keys=!__none__!__none__&max_channel_version=nightly%252F47&measure=CYCLE_COLLECTOR_MAX_PAUSE&min_channel_version=nightly%252F44&product=Firefox&sanitize=1&sort_keys=submissions&start_date=2016-01-25&trim=1&use_submission_date=0
The current telemetry UI is very good at hiding useful data :(
I had to explicitly enable 95th to see this.
Fix is now live.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 3•10 years ago
|
||
Thanks for fixing the UI, but this bug was about investigating a Firefox regression. :)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 4•10 years ago
|
||
It would be worth looking through the archives of the telemetry mailing list to see if it picked up any CC pause regressions. I'm not sure what it chooses to flag, though.
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•