New issue
Advanced search Search tips

Issue 699783 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

9.9% regression in media.tough_video_cases at 454741:454950

Project Member Reported by liberato@google.com, Mar 8 2017

Issue description

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

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


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

chromium-rel-win10

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: a5dfa06213d12fcabc014e6eacb73c199fd5a53e
  bad_revision : a35616e32425b2ff9d044bdc705ccc3542077b51

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : media.tough_video_cases
  Metric       : vm_working_set_delta_size/tulip2.wav_renderer

Revision                           Result                  N
chromium@454740                    4560.67 +- 165.062      6      good
chromium@454790                    4454.0 +- 393.334       6      good
chromium@454793                    4403.33 +- 144.379      6      good
chromium@454793,v8@2362f869a4      4472.67 +- 238.423      6      good
chromium@454793,v8@08d84f6d23      4443.33 +- 393.727      6      good
chromium@454793,v8@a5dfa06213      4634.67 +- 571.305      6      good
chromium@454793,v8@a35616e324      5140.0 +- 326.19        6      bad
chromium@454793,v8@a6b20adbf9      5162.67 +- 195.441      6      bad
chromium@454793,v8@59c9e6ff69      5228.67 +- 245.824      6      bad
chromium@454794                    5200.67 +- 187.737      6      bad
chromium@454795                    5026.67 +- 353.527      6      bad
chromium@454796                    5028.0 +- 246.382       6      bad
chromium@454802                    5192.0 +- 182.954       6      bad
chromium@454812                    5014.0 +- 120.632       6      bad
chromium@454833                    5224.0 +- 255.249       6      bad
chromium@454950                    5071.33 +- 350.79       6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests media.tough_video_cases

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8985647430069691440

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5770630189809664


| 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 Speed>Bisection.  Thank you!
Project Member

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

Mergedinto: 697879
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Toon Verwaest
  Commit : 6477f0777f57736411a02837301451ffb0e349ff
  Date   : Tue Feb 28 14:08:05 2017
  Subject: [api] Mark api prototypes as prototype before configuring them

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : media.tough_video_cases
  Metric       : vm_working_set_delta_size/tulip2.wav_renderer
  Change       : 17.51% | 4330.0 -> 5088.0

Revision                           Result                  N
chromium@454740                    4330.0 +- 178.595       6      good
chromium@454793                    4330.67 +- 165.28       6      good
chromium@454793,v8@2362f869a4      4452.67 +- 330.111      6      good
chromium@454793,v8@08d84f6d23      4417.33 +- 449.592      6      good
chromium@454793,v8@a5dfa06213      4442.67 +- 308.216      6      good
chromium@454793,v8@6477f0777f      5100.0 +- 153.467       6      bad       <--
chromium@454793,v8@a35616e324      5174.67 +- 340.149      6      bad
chromium@454793,v8@a6b20adbf9      5136.67 +- 279.395      6      bad
chromium@454793,v8@59c9e6ff69      5260.67 +- 295.373      6      bad
chromium@454794                    5214.0 +- 328.962       6      bad
chromium@454795                    5124.0 +- 239.466       6      bad
chromium@454797                    5141.33 +- 241.97       6      bad
chromium@454800                    5214.0 +- 130.323       6      bad
chromium@454806                    5130.0 +- 305.876       6      bad
chromium@454819                    5158.67 +- 154.575      6      bad
chromium@454845                    5132.0 +- 261.626       6      bad
chromium@454950                    5088.0 +- 436.715       6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests media.tough_video_cases

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8985491312972671424

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=4586602329800704


| 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 Speed>Bisection.  Thank you!

Sign in to add a comment