New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 823162 link

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

Blocking:
issue angleproject:2389



Sign in to add a comment

11.6% regression in angle_perftests at 543252:543307

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

Comment 1 by 42576172...@developer.gserviceaccount.com, Mar 19 2018 

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

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


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

chromium-rel-win7-gpu-nvidia

Comment 4 by jmad...@chromium.org, Mar 19 2018

Cc: -jmadill@google.com
Components: Internals>GPU>ANGLE
Labels: OS-Windows
Owner: jmad...@chromium.org
Status: Assigned (was: Untriaged)
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Mar 19 2018

Cc: fjhenigman@chromium.org jmad...@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/149bf0f9440000

VertexArray: Add perf tests for VAO dirty bits. by jmadill@chromium.org
https://chromium.googlesource.com/angle/angle/+/1b14d7cec16e54b4f27c50ef7b6cdb95c15911ea

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

Comment 6 by 42576172...@developer.gserviceaccount.com, Mar 19 2018 

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/12a572f1440000

VertexArray: Add perf tests for VAO dirty bits. by jmadill@chromium.org
https://chromium.googlesource.com/angle/angle/+/1b14d7cec16e54b4f27c50ef7b6cdb95c15911ea

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

Comment 7 by jmad...@chromium.org, Mar 19 2018

Status: WontFix (was: Assigned)
Realistically can't think of a real regression that could be caused by adding a new perf test - but it does seem possible this caused some noise in the tests. Closing as WontFix as both pinpoint jobs found the perf test CL.

Comment 8 by jmad...@chromium.org, Mar 19 2018

Blocking: angleproject:2389
►

Sign in to add a comment