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

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


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

linux-perf

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/12d619a9a40000

📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/12d619a9a40000

Run font_service in-browser by drott@chromium.org
https://chromium.googlesource.com/chromium/src/+/b40906acf189f7764d0c75a173c2e03cc55eb620
1.293 → 1.354 (+0.061)

Move persistent notification id from notification database to profile. by yangsharon@google.com
https://chromium.googlesource.com/chromium/src/+/c6706906e35d96358fa5a8a78931c0452fe098c2
1.445 → 1.431 (-0.01377)

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

This regression is a rebound after ac24004e3831e8a63a80c90cffbcbdd52b398e7c meant an improvement of about the same amount. In ac24004e3831e8a63a80c90cffbcbdd52b398e7c FontConfig calls were moved to Mojo to an out of process utility service. In b40906acf189f7764d0c75a173c2e03cc55eb620 these methods were moved back in-process which removes the improvement, but is necessary for reducing the memory overhead of having a separate process.

 Issue 864534  has been merged into this issue.

 Issue 865581  has been merged into this issue.

 Issue 865664  has been merged into this issue.