Issue metadata
Sign in to add a comment
|
225.3%-280.2% regression in loading.mobile at 532892:533108 |
||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Feb 2 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/159eb49e840000
,
Feb 9 2018
📍 Found significant differences after each of 2 commits. https://pinpoint-dot-chromeperf.appspot.com/job/159eb49e840000 [scheduler] Experiment to always treat input events as high-priority. by altimin@chromium.org chromium @ ef42564665d915f2d2294d0bfa3a9ab5632c9777 Remove unused UMAUploadScheduler params. by holte@google.com chromium @ a2c0263a67cc17a24bd38312d1f5ada95c818731 Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Feb 13 2018
The "Remove unused UMAUploadScheduler params." is a no-op CL, so it can't cause a regression. Over to altimin@ for the other CL.
,
Mar 28 2018
Ping - has this performance regression been looked at?
,
May 24 2018
|
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Feb 2 2018