Issue metadata
Sign in to add a comment
|
3.6% regression in rendering.desktop at 575372:575398 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 19
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/10162b99a40000
,
Jul 20
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/10162b99a40000
,
Jul 20
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/142da53ea40000
,
Jul 20
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/142da53ea40000
,
Jul 20
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/122a6969a40000
,
Jul 21
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/122a6969a40000 Roll fontconfig to d1f48f11 by thomasanderson@chromium.org https://chromium.googlesource.com/chromium/src/+/3ff47e60c5ce645973e57fc8dbe88b43d63edaf4 17.01 → 17.31 (+0.2986) Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Jul 23
Original fontconfig roll introduced a bug: https://chromium.googlesource.com/chromium/src/+/a0c1584a2fade0146b7cd3380abe42feda02ad7c Subsequent fontconfig roll fixed the regression introduced in the previous roll: https://chromium.googlesource.com/chromium/src/+/a0c1584a2fade0146b7cd3380abe42feda02ad7c The graphs indicate a performance improvement on the original roll that introduced the bug, and a regression after. These performance differences are expected due to the nature of the bug introduced and then fixed. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jul 19