Issue metadata
Sign in to add a comment
|
3.7%-52.8% regression in v8.runtimestats.browsing_desktop at 478248:478369 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jun 14 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976800448389591584
,
Jun 14 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: mac_10_12_perf_bisect Benchmark : v8.runtimestats.browsing_desktop Metric : Parse-Background:duration_avg/browse_news/browse_news_reddit Revision Result N chromium@478247 669.088 +- 346.759 21 good chromium@478310 663.385 +- 250.023 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.reddit v8.runtimestats.browsing_desktop Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8976800448389591584 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4996874588651520 | 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!
,
Jun 14 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976789175824943376
,
Jun 14 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: mac_10_12_perf_bisect Benchmark : v8.runtimestats.browsing_desktop Metric : Parse-Background:duration_avg/browse_news/browse_news_reddit Revision Result N chromium@478247 671.744 +- 220.946 21 good chromium@478310 670.988 +- 278.999 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.reddit v8.runtimestats.browsing_desktop Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8976789175824943376 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4996874588651520 | 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!
,
Jun 15 2017
Assigning to performance sheriff.
,
Jun 16 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976647596997361312
,
Jun 16 2017
=== Auto-CCing suspected CL author sky@chromium.org === Hi sky@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 : Scott Violet Commit : c510f5fdf094f135e32b42f33e23a8152af4b881 Date : Fri Jun 09 17:07:21 2017 Subject: chromeos: adds InputDeviceController mojo interface Bisect Details Configuration: winx64intel_perf_bisect Benchmark : v8.runtimestats.browsing_desktop Metric : Compile:duration_avg/browse_social/browse_social_facebook_infinite_scroll Change : 4.88% | 127.188333333 -> 133.3965 Revision Result N chromium@478280 127.188 +- 4.89115 6 good chromium@478303 126.066 +- 2.07457 6 good chromium@478309 127.451 +- 4.30979 9 good chromium@478311 130.887 +- 5.8433 6 good chromium@478312 135.113 +- 4.16718 6 bad <-- chromium@478314 131.692 +- 2.79635 6 bad chromium@478325 132.489 +- 6.09864 6 bad chromium@478369 133.396 +- 3.83349 6 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.social.facebook.infinite.scroll v8.runtimestats.browsing_desktop Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8976647596997361312 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4839060310327296 | 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 tebbi@chromium.org
, Jun 14 2017