Issue metadata
Sign in to add a comment
|
12.1%-38.2% regression in v8.runtimestats.browsing_mobile at 508720:508852 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Oct 17 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8965499353512691392
,
Oct 17 2017
=== Auto-CCing suspected CL author hans@chromium.org === Hi hans@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 : Hans Wennborg Commit : 8316001e3f423f6ca2e7a9a7258c22944d16ae13 Date : Fri Oct 13 20:32:51 2017 Subject: Roll Clang 313786:315613 Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : v8.runtimestats.browsing_mobile Metric : v8-gc-incremental-step_max/browse_social/browse_social_pinterest_infinite_scroll Change : 40.40% | 18.088 -> 25.3948333333 Revision Result N chromium@508719 18.088 +- 2.98685 6 good chromium@508786 17.711 +- 1.91581 6 good chromium@508803 16.8992 +- 3.48512 6 good chromium@508804 25.824 +- 3.92332 6 bad <-- chromium@508805 26.4607 +- 3.28172 6 bad chromium@508807 25.4988 +- 4.81504 6 bad chromium@508811 23.964 +- 5.64017 6 bad chromium@508819 24.3408 +- 5.40229 6 bad chromium@508852 25.3948 +- 7.91856 6 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.pinterest.infinite.scroll 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/8965499353512691392 For feedback, file a bug with component Speed>Bisection
,
Oct 17 2017
,
Oct 20 2017
,
Oct 23 2017
,
Jan 22 2018
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Oct 17 2017