New issue
Advanced search Search tips

Issue 831562 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1%-2% regression in angle_perftests at 543825:544117

Project Member Reported by jmadill@google.com, Apr 11 2018

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Apr 11 2018

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

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


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

chromium-rel-win7-gpu-nvidia
Cc: -jmad...@chromium.org
Components: Internals>GPU>ANGLE
Owner: jmad...@chromium.org
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Apr 11 2018

Cc: angle-ch...@skia-buildbots.google.com.iam.gserviceaccount.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/11f0f4fcc40000

Roll src/third_party/angle/ 3761dc7bf..e3dc5dd0c (1 commit) by angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/9404868df6ff64c42cee31cbe98928e1eac6dc49

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Cc: -angle-ch...@skia-buildbots.google.com.iam.gserviceaccount.com geoffl...@chromium.org
Status: WontFix (was: Assigned)
Not a visible regression. Though in the graph it looks as though the FixedVector change by Geoff improved the benchmark scores.

Sign in to add a comment