New issue
Advanced search Search tips

Issue 634316 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Nov 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

6.5% regression in angle_perftests at 409526:409569

Project Member Reported by jmad...@chromium.org, Aug 4 2016

Issue description

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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg5tH-rAoM


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

chromium-rel-win7-gpu-nvidia
Cc: jmad...@chromium.org

=== Auto-CCing suspected CL author jmadill@chromium.org ===

Hi jmadill@chromium.org, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : D3D11: Remove X24G8 special format.
Author  : Jamie Madill
Commit description:
  
This special format means we're using a depth/stencil format with only
the stencil channel being used. We can just use a normal D24S8 format
here, there's pretty much no difference.

BUG= angleproject:1455 

Change-Id: Id304094b92814f38930209a703733190ad8e8410
Reviewed-on: https://chromium-review.googlesource.com/359086
Reviewed-by: Corentin Wallez <cwallez@chromium.org>
Reviewed-by: Geoff Lang <geofflang@chromium.org>
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Commit  : 6bbdce5b366dd1adc09c69b5265bc585d08b2c20
Date    : Tue Aug 02 23:33:29 2016


===== TESTED REVISIONS =====
Revision                          Mean     Std Dev  N  Good?
chromium@409525                   29745.8  77.3156  5  good
chromium@409536                   29729.2  127.942  5  good
chromium@409542                   29708.6  109.534  5  good
chromium@409544                   29469.8  674.161  5  good
chromium@409544,angle@00d6796aba  29318.8  198.657  5  good
chromium@409544,angle@7a074768a9  30229.6  110.339  5  good
chromium@409544,angle@6bbdce5b36  28406.0  68.4215  5  bad    <--
chromium@409545                   27803.0  122.215  5  bad
chromium@409547                   27799.0  88.1391  5  bad
chromium@409569                   27714.6  74.9086  5  bad

Bisect job ran on: winx64nvidia_perf_bisect
Bug ID: 634316

Test Command: .\src\out\Release_x64\angle_perftests.exe --test-launcher-print-test-stdio=always --test-launcher-jobs=1
Test Metric: DrawCallPerf_d3d11_null/score
Relative Change: 6.83%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64nvidia_perf_bisect/builds/1784
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005250829488394384


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5236009340502016

| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!

===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : D3D11: Remove X24G8 special format.
Author  : Jamie Madill
Commit description:
  
This special format means we're using a depth/stencil format with only
the stencil channel being used. We can just use a normal D24S8 format
here, there's pretty much no difference.

BUG= angleproject:1455 

Change-Id: Id304094b92814f38930209a703733190ad8e8410
Reviewed-on: https://chromium-review.googlesource.com/359086
Reviewed-by: Corentin Wallez <cwallez@chromium.org>
Reviewed-by: Geoff Lang <geofflang@chromium.org>
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Commit  : 6bbdce5b366dd1adc09c69b5265bc585d08b2c20
Date    : Tue Aug 02 23:33:29 2016


===== TESTED REVISIONS =====
Revision                          Mean     Std Dev  N  Good?
chromium@409525                   29765.4  80.7886  5  good
chromium@409536                   29725.6  70.337   5  good
chromium@409542                   29782.8  55.6031  5  good
chromium@409544                   29531.2  488.304  5  good
chromium@409544,angle@00d6796aba  29377.6  66.6543  5  good
chromium@409544,angle@7a074768a9  30244.2  54.0065  5  good
chromium@409544,angle@6bbdce5b36  28348.2  69.9335  5  bad    <--
chromium@409545                   27854.6  149.746  5  bad
chromium@409547                   27759.6  163.176  5  bad
chromium@409569                   27886.4  45.1032  5  bad

Bisect job ran on: winx64nvidia_perf_bisect
Bug ID: 634316

Test Command: .\src\out\Release_x64\angle_perftests.exe --test-launcher-print-test-stdio=always --test-launcher-jobs=1
Test Metric: DrawCallPerf_d3d11_null/score
Relative Change: 6.31%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64nvidia_perf_bisect/builds/1783
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005254702403128496


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6470218927308800

| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!
Status: WontFix (was: Assigned)

Sign in to add a comment