New issue
Advanced search Search tips

Issue 757928 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 757342
Owner: ----
Closed: Aug 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

51.8% regression in runs/s clockless_playback sfx_u8.wav - media_perftests at 495385:495501

Project Member Reported by chcunningham@chromium.org, Aug 22 2017

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Aug 22 2017

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

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


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

chromium-rel-win8-dual
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Aug 22 2017


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : media_perftests
  Metric       : clockless_playback/sfx_u8.wav

Revision             Result                  N
chromium@495384      6702.48 +- 2860.09      21      good
chromium@495501      6805.75 +- 2991.14      21      bad

To Run This Test
  .\src\out\Release\media_perftests.exe --single-process-tests

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8970535153728088816


For feedback, file a bug with component Speed>Bisection
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Aug 23 2017

Mergedinto: 757342
Status: Duplicate (was: Untriaged)

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Nico Weber
  Commit : 7cd2f6bd73c6a9c6200704e995b18ebb3168ead6
  Date   : Sat Aug 19 04:23:54 2017
  Subject: win: Turn off clang-by-default again for now.

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : media_perftests
  Metric       : clockless_playback/sfx_u8.wav
  Change       : 53.07% | 9300.61225681 -> 4364.47139748

Revision             Result                  N
chromium@494003      9300.61 +- 3768.36      6      good
chromium@494918      7474.25 +- 2382.32      6      good
chromium@495375      6042.57 +- 925.526      6      good
chromium@495604      6420.31 +- 1788.91      6      good
chromium@495718      6130.54 +- 1482.68      6      good
chromium@495775      6123.08 +- 329.919      6      good
chromium@495790      6870.92 +- 1953.12      6      good
chromium@495797      6234.32 +- 1629.44      6      good
chromium@495801      6797.05 +- 1252.63      6      good
chromium@495802      3434.96 +- 539.28       6      bad       <--
chromium@495803      3538.04 +- 304.316      6      bad
chromium@495804      3246.92 +- 825.243      6      bad
chromium@495832      4364.47 +- 855.732      6      bad

To Run This Test
  .\src\out\Release\media_perftests.exe --single-process-tests

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8970527181752482192


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment