New issue
Advanced search Search tips

Issue 740667 link

Starred by 0 users

Issue metadata

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



Sign in to add a comment

18.9% regression in media_perftests at 485087:485139

Project Member Reported by zhanliang@google.com, Jul 10 2017

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jul 10 2017

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

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


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

chromium-rel-win7-gpu-nvidia
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jul 10 2017


=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: winx64nvidia_perf_bisect
  Benchmark    : media_perftests
  Metric       : audio_converter/convert_pass_through


To Run This Test
  .\src\out\Release_x64\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/8974425533695018416


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

Comment 5 by 42576172...@developer.gserviceaccount.com, Jul 11 2017

Cc: holte@chromium.org
Owner: holte@chromium.org

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

Hi holte@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : holte
  Commit : 094e496b0751a1efa5463cba8662318499d1fec8
  Date   : Fri Jul 07 23:13:48 2017
  Subject: Disable UKM on Android

Bisect Details
  Configuration: winx64nvidia_perf_bisect
  Benchmark    : media_perftests
  Metric       : audio_converter/convert_pass_through
  Change       : 0.35% | 2054635.96554 -> 2061903.16744

Revision             Result                  N
chromium@485086      2054636 +- 46604.4      21      good
chromium@485087      2056725 +- 43347.9      14      good
chromium@485088      2071476 +- 26633.9      14      bad       <--
chromium@485090      2083369 +- 17602.2      6       bad
chromium@485093      2075091 +- 20126.3      6       bad
chromium@485100      2073614 +- 27520.8      6       bad
chromium@485113      2086288 +- 19794.9      6       bad
chromium@485139      2061903 +- 36112.5      21      bad

To Run This Test
  .\src\out\Release_x64\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/8974415865602521312


For feedback, file a bug with component Speed>Bisection

Comment 6 by holte@chromium.org, Jul 11 2017

That CL is an implausible culprit, it has no behavior change on windows.
Cc: -holte@chromium.org
Owner: ----
Project Member

Comment 9 by 42576172...@developer.gserviceaccount.com, Jul 11 2017


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

Bisect Details
  Configuration: winx64nvidia_perf_bisect
  Benchmark    : media_perftests
  Metric       : audio_converter/convert_pass_through

Revision             Result                  N
chromium@484978      2068192 +- 118770       21      good
chromium@485148      2062111 +- 81745.9      21      bad

To Run This Test
  .\src\out\Release_x64\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/8974405928465133056


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

Comment 10 by sheriffbot@chromium.org, Jul 11 2017

Labels: Hotlist-Google
Status: WontFix (was: Untriaged)

Sign in to add a comment