New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 700827 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 697879
Owner:
Last visit > 30 days ago
Closed: Mar 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

86.4% regression in v8.runtimestats.browsing_mobile_turbo at 454688:454883

Project Member Reported by hpayer@google.com, Mar 13 2017

Issue description

See the link to graphs below.
 

Comment 1 by hpayer@google.com, Mar 13 2017

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

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


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

android-nexus5X
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Mar 13 2017

Mergedinto: 697879
Status: Duplicate (was: Assigned)

=== 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: android_nexus5X_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile_turbo
  Metric       : v8-gc-full-mark-compactor_sum/browse_social/browse_social_twitter
  Change       : 106.52% | 19.9162857143 -> 41.1303333333

Revision                           Result                  N
chromium@454687                    19.9163 +- 19.4467      7       good
chromium@454791                    21.1291 +- 14.6263      10      good
chromium@454793                    20.4882 +- 19.8111      10      good
chromium@454793,v8@2362f869a4      25.0838 +- 15.2708      5       good
chromium@454793,v8@09a07038f2      23.06 +- 6.80919        4       good
chromium@454793,v8@a5dfa06213      19.5917 +- 7.43581      3       good
chromium@454793,v8@6477f0777f      38.1822 +- 37.0866      14      bad       <--
chromium@454793,v8@a35616e324      35.6469 +- 29.0509      14      bad
chromium@454793,v8@a6b20adbf9      36.2735 +- 26.3418      14      bad
chromium@454793,v8@59c9e6ff69      37.0829 +- 30.1094      14      bad
chromium@454794                    35.0601 +- 23.5253      14      bad
chromium@454797                    34.6117 +- 13.9694      6       bad
chromium@454803                    36.6715 +- 17.9072      6       bad
chromium@454814                    35.0068 +- 34.4208      14      bad
chromium@454837                    38.4626 +- 38.7661      14      bad
chromium@454883                    41.1303 +- 21.0115      9       bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.social.twitter v8.runtimestats.browsing_mobile_turbo

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

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


| 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