New issue
Advanced search Search tips

Issue 865666 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jul 20
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3%-108.8% regression in system_health.common_desktop at 575372:575398

Project Member Reported by npm@chromium.org, Jul 19

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=865666

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


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

linux-perf
Cc: thomasanderson@chromium.org
Owner: thomasanderson@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/104b62d1a40000

Roll fontconfig to d1f48f11 by thomasanderson@chromium.org
https://chromium.googlesource.com/chromium/src/+/3ff47e60c5ce645973e57fc8dbe88b43d63edaf4
245 → 448 (+203)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Status: WontFix (was: Assigned)
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.

Sign in to add a comment