New issue
Advanced search Search tips

Issue 854419 link

Starred by 1 user
Status: WontFix
Owner:
jmad...@chromium.org
Closed: Jun 2018
Cc:
h...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

6.9% regression in angle_perftests at 566139:566309

Project Member Reported by jmadill@google.com, Jun 20 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jun 20 2018 

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

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


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

chromium-rel-win7-gpu-nvidia
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jun 20 2018

Cc: h...@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1495e45d240000

Roll clang 332838:334100. by hans@chromium.org
https://chromium.googlesource.com/chromium/src/+/9fdb571a3bb12cf34eb24ba00808754b5897ee23
7231 → 6733 (-497.7)

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

Comment 4 by jmad...@chromium.org, Jun 20 2018

Status: WontFix (was: Assigned)
hans, is there a tracking bug for regressions with the Clang roll? Closing this as WontFix. Seems related to Clang code gen.

Comment 5 by jmad...@chromium.org, Jun 20 2018

Components: Internals>GPU>ANGLE

Comment 6 by h...@chromium.org, Jun 20 2018 

No tracking bug for the latest roll, no.

Looking at the graph, it seems like some of the performance was returning lately, so I'm not sure there's much to do here.
►

Sign in to add a comment