New issue
Advanced search Search tips

Issue 700300 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

31.3%-36.5% regression in v8.runtimestats.browsing_mobile_turbo at 454759:454889

Project Member Reported by tebbi@chromium.org, Mar 10 2017

Issue description

See the link to graphs below.
 

Comment 1 by tebbi@chromium.org, Mar 10 2017

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

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


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

android-webview-nexus5X
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Mar 10 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: android_webview_arm64_aosp_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile_turbo
  Metric       : Compile:duration_avg/browse_social/browse_social_twitter
  Change       : 33.59% | 150.096333333 -> 200.508666667

Revision                           Result                  N
chromium@454758                    150.096 +- 39.2783      6       good
chromium@454791                    168.978 +- 91.506       14      good
chromium@454793                    165.226 +- 108.814      21      good
chromium@454793,v8@2362f869a4      169.703 +- 87.1166      14      good
chromium@454793,v8@08d84f6d23      161.672 +- 66.3681      9       good
chromium@454793,v8@a5dfa06213      162.149 +- 80.8756      14      good
chromium@454793,v8@6477f0777f      193.669 +- 26.5895      9       bad       <--
chromium@454793,v8@a35616e324      197.983 +- 21.7508      6       bad
chromium@454793,v8@a6b20adbf9      192.123 +- 63.009       14      bad
chromium@454793,v8@59c9e6ff69      197.608 +- 21.8971      9       bad
chromium@454794                    192.584 +- 54.6446      14      bad
chromium@454796                    195.802 +- 20.3743      9       bad
chromium@454800                    199.678 +- 12.4751      6       bad
chromium@454808                    191.946 +- 55.5997      14      bad
chromium@454824                    195.133 +- 18.3126      9       bad
chromium@454889                    200.509 +- 7.46765      6       bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --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/8985518576759905904

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


| 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