Issue metadata
Sign in to add a comment
|
11.3%-237% regression in v8.runtimestats.browsing_desktop at 477086:493971 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 14 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8971300111898721328
,
Aug 15 2017
=== BISECT JOB RESULTS === Bisect was unable to run to completion Error: INFRA_FAILURE The bisect was able to narrow the range, you can try running with: good_revision: af46af9f93aad007a4bd053612733592ea781981 bad_revision : f0c3c780c8297209abc2a7e8f9b2efb63d064436 If failures persist contact the team (see below) and report the error. Bisect Details Configuration: win_8_perf_bisect Benchmark : v8.runtimestats.browsing_desktop Metric : v8-gc-incremental-step_max/browse_social/browse_social_twitter Revision Result N chromium@493054 1.69083 +- 0.462077 6 good chromium@493288 1.69867 +- 0.242754 6 good chromium@493345 1.67117 +- 0.258079 6 good chromium@493359 1.72733 +- 0.334155 6 good chromium@493366 1.6065 +- 0.166978 6 good chromium@493373 1.27283 +- 0.33817 6 bad chromium@493401 1.33067 +- 0.287175 6 bad chromium@493513 1.23789 +- 0.275163 9 bad chromium@493971 1.18367 +- 0.0853776 6 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.social.twitter v8.runtimestats.browsing_desktop More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8971300111898721328 For feedback, file a bug with component Speed>Bisection
,
Aug 16 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8971114428048155936
,
Mar 14 2018
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 14 2017