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

Issue 816464 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

10.6% regression in angle_perftests at 538408:538459

Project Member Reported by jmadill@google.com, Feb 26 2018

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Feb 26 2018

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

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


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

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

Comment 4 by 42576172...@developer.gserviceaccount.com, Feb 26 2018

Cc: kkhorimoto@chromium.org roc...@chromium.org gayane@chromium.org thestig@chromium.org fdoray@chromium.org gab@chromium.org rch@chromium.org
Owner: fdoray@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/13991670440000

Remove SequencedWorkerPool. by fdoray@chromium.org
https://chromium.googlesource.com/chromium/src/+/4914ec14f5baf0bfdc7ca1733391358f60cec360

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

Comment 5 by fdoray@chromium.org, Feb 26 2018

Owner: jmad...@chromium.org
My CL removed unused code. I doubt that it caused a performance regression.
Cc: simonhatch@chromium.org
Status: WontFix (was: Assigned)
Probably more optimizer noise. Closing as WontFix. (fyi Simon)

Sign in to add a comment