New issue
Advanced search Search tips

Issue 659698 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

5.3% regression in angle_perftests/Textures_d3d11_8_textures_5_rebind_3_state_8_mips/score on chromium-rel-win7-gpu-nvidia at 427479:427537

Project Member Reported by jmad...@chromium.org, Oct 26 2016

Issue description

Performance dashboard identified a 5.3% regression in angle_perftests/Textures_d3d11_8_textures_5_rebind_3_state_8_mips/score on chromium-rel-win7-gpu-nvidia at revision range 427479:427537. Graph: https://chromeperf.appspot.com/report?masters=ChromiumPerf&bots=chromium-rel-win7-gpu-nvidia&tests=angle_perftests%2FTextures_d3d11_8_textures_5_rebind_3_state_8_mips%2Fscore&checked=score%2Cscore_ref%2Cref&rev=427537

Geoff can you investigate? I also recommend you rename these tests to not have this ridiculous number of parameters in the name. I think I suggested you do this in the code review as well.
 
Project Member

Comment 2 by 42576172...@developer.gserviceaccount.com, Oct 27 2016

Cc: geoffl...@chromium.org

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

Hi geofflang@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 : Add stubs for EGL_EXT_swap_buffers_with_damage.
Author  : Geoff Lang
Commit description:
  
BUG= 512090 

Change-Id: I9413d6f5c13b9ea59ab9c923dc6c5d157f344166
Reviewed-on: https://chromium-review.googlesource.com/291652
Commit-Queue: Geoff Lang <geofflang@chromium.org>
Reviewed-by: Jamie Madill <jmadill@chromium.org>
Commit  : a284f2ff19d51d6e06c216772d69dff25e189dc3
Date    : Mon Oct 24 17:35:47 2016


===== TESTED REVISIONS =====
Revision                          Mean    Std Dev  N  Good?
chromium@427191                   1589.6  10.5024  5  good
chromium@427218                   1594.0  5.61249  5  good
chromium@427225                   1594.8  6.45755  5  good
chromium@427227                   1596.4  5.94138  5  good
chromium@427227,angle@a284f2ff19  1557.4  5.17687  5  bad    <--
chromium@427227,angle@7efe747cb0  1554.0  23.0868  5  bad
chromium@427227,angle@2a1e8b6b06  1561.6  6.58027  5  bad
chromium@427228                   1559.2  6.6106   5  bad
chromium@427229                   1560.8  4.81664  5  bad
chromium@427232                   1569.8  1.30384  5  bad
chromium@427245                   1561.6  7.50333  5  bad

Bisect job ran on: winx64nvidia_perf_bisect
Bug ID: 659698

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

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


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

| 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)
Closing this, we never got a good regression range.

Sign in to add a comment