New issue
Advanced search Search tips

Issue 738828 link

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



Sign in to add a comment

87.5% regression in v8.runtimestats.browsing_mobile at 483765:483838

Project Member Reported by jgruber@chromium.org, Jul 3 2017 
See the link to graphs below.

Comment 1 by jgruber@chromium.org, Jul 3 2017 

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

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


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

android-webview-nexus5X
Project Member

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


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

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-scavenger_max/browse_social/browse_social_twitter

Revision             Result                  N
chromium@483764      8.856 +- 5.02658        21      good
chromium@483838      9.56295 +- 4.97133      21      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

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8975103004486939680


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

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


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

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-scavenger_max/browse_social/browse_social_twitter

Revision             Result                  N
chromium@483764      8.24795 +- 6.91594      21      good
chromium@483838      9.60681 +- 5.7329       21      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

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8975071416186061504


For feedback, file a bug with component Speed>Bisection

Comment 7 by jgruber@chromium.org, Jul 4 2017 

Probably 738718.
Project Member

Comment 8 by 42576172...@developer.gserviceaccount.com, Jul 4 2017 


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

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-scavenger_max/browse_social/browse_social_twitter

Revision             Result                  N
chromium@483764      9.02614 +- 4.71134      21      good
chromium@483838      9.67957 +- 4.65859      21      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

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8975021486577702720


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

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


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

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-scavenger_max/browse_social/browse_social_twitter

Revision             Result                  N
chromium@483764      8.629 +- 7.52001        21      good
chromium@483838      8.67481 +- 7.70759      21      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

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8975014795695925136


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

Comment 12 by 42576172...@developer.gserviceaccount.com, Jul 8 2017 


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

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-scavenger_max/browse_social/browse_social_twitter

Revision             Result                  N
chromium@483764      8.64619 +- 6.84657      21      good
chromium@483838      8.40405 +- 6.71832      21      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

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8974749038635955040


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

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

Mergedinto: 738718
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Ulan Degenbaev
  Commit : f341bb0f623821e56349735e47e1a9094f65d9a3
  Date   : Fri Jun 30 12:03:04 2017
  Subject: Revert "[heap] Allow a minimum semi-space size of 512K."

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-scavenger_max/browse_social/browse_social_twitter
  Change       : 96.88% | 4.324 -> 8.51316666667

Revision                           Result                  N
chromium@483695                    4.324 +- 4.3187         9      good
chromium@483713                    4.99856 +- 5.48221      9      good
chromium@483722                    4.93456 +- 4.72034      9      good
chromium@483727                    5.28922 +- 5.84638      9      good
chromium@483729                    5.25217 +- 3.87546      6      good
chromium@483729,v8@ca93156294      3.81533 +- 1.00399      6      good
chromium@483729,v8@f341bb0f62      8.64683 +- 3.34584      6      bad       <--
chromium@483729,v8@fa4314da8b      8.8865 +- 3.66233       6      bad
chromium@483729,v8@bfbabce113      9.2855 +- 2.75494       6      bad
chromium@483730                    9.6125 +- 1.4652        6      bad
chromium@483731                    8.715 +- 5.63568        9      bad
chromium@483767                    10.2963 +- 3.23838      6      bad
chromium@483838                    8.51317 +- 4.93205      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

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8974460913780412608


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

Sign in to add a comment