All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=855990

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=7c4a30c3e0badaa78b9c3deda87e14d036ab6cf0697690560240d5967b3a74d7


Bot(s) for this bug's original alert(s):

linux-perf

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14cdaee0a40000

📍 Found significant differences after each of 3 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/14cdaee0a40000

Initial commit of a basic Content Service by rockot@chromium.org
https://chromium.googlesource.com/chromium/src/+/84f58fd64c2aa9cbe2d4f6b356fb8a5a695092ce
0.04415 → 0.0449 (+0.00075)

Remove blanks facility from the library by behdad@behdad.org
https://chromium.googlesource.com/external/fontconfig/+/8f4c4d278d013f6cc69ba7d7bf0f8aed11398dfb
0.04463 → No values

Reland "Reland "Update fontconfig to 6cc99d6a"" by thomasanderson@chromium.org
https://chromium.googlesource.com/chromium/src/+/a0c1584a2fade0146b7cd3380abe42feda02ad7c
No values → 0.0472

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

BULK EDIT

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.