Issue metadata
Sign in to add a comment
|
148.7%-734.7% regression in v8.runtimestats.browsing_mobile_classic at 469616:469644 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
May 8 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8980168621063831392
,
May 8 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : v8.runtimestats.browsing_mobile_classic Metric : v8-gc-memory-mark-compactor_sum/browse_social/browse_social_twitter Revision Result N chromium@469615 50.6616 +- 48.7894 21 good chromium@469644 52.9434 +- 66.7277 21 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_classic Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8980168621063831392 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5810652284715008 | 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!
,
May 8 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8980163909607977104
,
May 8 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : v8.runtimestats.browsing_mobile_classic Metric : v8-gc-memory-mark-compactor_sum/browse_social/browse_social_twitter Revision Result N chromium@469615 58.1507 +- 64.5196 21 good chromium@469644 53.0854 +- 71.1823 21 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_classic Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8980163909607977104 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5810652284715008 | 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!
,
May 8 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8980158122125097056
,
May 8 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : hpayer Commit : 8833af23e9788c725b0887446915e4820383a385 Date : Fri May 05 11:24:02 2017 Subject: [heap] Memory reducer calls GC with kGCCallbackFlagCollectAllExternalMemory flag. Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : v8.runtimestats.browsing_mobile_classic Metric : v8-gc-memory-mark-compactor_max/browse_social/browse_social_twitter Change : 74.16% | 12.7805 -> 22.2583333333 Revision Result N chromium@469595 12.7805 +- 6.44345 6 good chromium@469628 14.9247 +- 8.01098 6 good chromium@469644 13.7947 +- 10.1359 6 good chromium@469652 12.9411 +- 11.1692 9 good chromium@469654 15.2343 +- 14.9848 9 good chromium@469654,v8@25959abf79 10.3505 +- 4.58288 6 good chromium@469654,v8@b7b3781b87 11.9848 +- 8.62668 6 good chromium@469654,v8@8833af23e9 22.316 +- 8.67501 9 bad <-- chromium@469655 24.2717 +- 8.09557 6 bad chromium@469656 22.2903 +- 4.04915 6 bad chromium@469660 22.2583 +- 3.71223 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.twitter v8.runtimestats.browsing_mobile_classic Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8980158122125097056 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6581294911193088 | 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 |
|||||||||||||||||||||||
Comment 1 by mlippautz@google.com
, May 8 2017