New issue
Advanced search Search tips

Issue 758693 link

Starred by 1 user
Status: Duplicate
Merged: issue 757342
Owner: ----
Closed: Aug 2017
Cc:
chcunningham@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

32.9% regression in media_perftests at 495543:495660

Project Member Reported by chcunningham@chromium.org, Aug 24 2017 
See the link to graphs below.
Project Member

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

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

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


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

chromium-rel-win7-dual
Project Member

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


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

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : media_perftests
  Metric       : clockless_playback/sfx.flac

Revision             Result                  N
chromium@495542      12193.9 +- 7055.22      21      good
chromium@495660      12304.2 +- 5864.28      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/8970347118202406320


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

Comment 5 by 42576172...@developer.gserviceaccount.com, Aug 25 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_perf_bisect
  Benchmark    : media_perftests
  Metric       : clockless_playback/sfx.flac
  Change       : 41.97% | 12999.0983908 -> 7543.36102576

Revision             Result                  N
chromium@494007      12999.1 +- 3083.64      6      good
chromium@495427      11739.1 +- 2546.01      6      good
chromium@495782      12788.6 +- 4978.85      6      good
chromium@495794      11255.0 +- 2426.69      6      good
chromium@495800      11016.6 +- 5107.04      6      good
chromium@495801      13145.5 +- 2739.14      6      good
chromium@495802      7352.85 +- 1215.6       6      bad       <--
chromium@495803      7737.18 +- 2044.51      6      bad
chromium@495805      7506.39 +- 1173.55      6      bad
chromium@495827      7253.44 +- 1174.64      6      bad
chromium@495871      7608.96 +- 401.272      6      bad
chromium@495960      7817.41 +- 813.665      6      bad
chromium@496137      7764.22 +- 1131.32      6      bad
chromium@496847      7543.36 +- 1072.08      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/8970337000929311056


For feedback, file a bug with component Speed>Bisection
►

Sign in to add a comment