Issue metadata
Sign in to add a comment
|
23.6%-181.7% regression in v8.browsing_mobile at 505527:505641 |
||||||||||||||||||||
Issue descriptionProblematic across the board.
,
Oct 4 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8966669379835205808
,
Oct 4 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Ulan Degenbaev Commit : 7c1b01154a460dec5da40a9c8d5ae4e44eea8e4e Date : Fri Sep 29 11:38:50 2017 Subject: [heap] Enable concurrent marking on all platforms. Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : v8.browsing_mobile Metric : v8-gc-total_avg/browse_tech/browse_tech_discourse_infinite_scroll Change : 95.58% | 1.30030113877 -> 2.54316116961 Revision Result N chromium@505526 1.3003 +- 0.320374 9 good chromium@505547 1.14315 +- 0.424301 6 good chromium@505558 1.13629 +- 0.331953 6 good chromium@505558,v8@5005a62fe0 1.32037 +- 0.283342 6 good chromium@505558,v8@7c1b01154a 3.2825 +- 0.84569 6 bad <-- chromium@505559 2.80708 +- 1.72559 6 bad chromium@505560 2.64223 +- 2.4357 9 bad chromium@505561 2.84677 +- 1.45938 6 bad chromium@505563 2.68213 +- 1.41329 6 bad chromium@505568 2.54316 +- 2.1538 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.tech.discourse.infinite.scroll v8.browsing_mobile More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8966669379835205808 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Oct 4 2017