New issue
Advanced search Search tips

Issue 876496 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Aug 27
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

14.4% regression in blink_perf.css at 582937:582969

Project Member Reported by hjd@google.com, Aug 21

Issue description

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

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


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

Android Nexus5X WebView Perf
Cc: h...@chromium.org
Owner: h...@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/128c4f8a640000

Re-land "Roll clang 337439:338452." by hans@chromium.org
https://chromium.googlesource.com/chromium/src/+/d74b4a7338023093d2cc0ada1c8d9964e1f1faf8
691.1 → 604.2 (-86.96)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Status: WontFix (was: Assigned)
Looking at the graph, the perf seems to have recovered.

Sign in to add a comment