Issue metadata
Sign in to add a comment
|
200.8%-3696.7% regression in v8.runtimestats.browsing_desktop at 483316:483416 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 2 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8975165074511436880
,
Jul 3 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: winx64intel_perf_bisect Benchmark : v8.runtimestats.browsing_desktop Metric : total:500ms_window:renderer_eqt:v8:gc:full-mark-compactor_max/total:500ms_window:renderer_eqt:v8:gc:full-mark-compactor_max 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 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/8975165074511436880 For feedback, file a bug with component Speed>Bisection
,
Jul 3 2017
Starting another bisect and assigning to this weeks' perf sheriff.
,
Jul 3 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8975072738193478944
,
Jul 3 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8975071420013094768
,
Jul 4 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: winx64ati_perf_bisect Benchmark : v8.runtimestats.browsing_desktop Metric : total:500ms_window:renderer_eqt:v8:gc_max/total:500ms_window:renderer_eqt:v8:gc_max 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 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/8975072738193478944 For feedback, file a bug with component Speed>Bisection
,
Jul 4 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8974980822404684400
,
Jul 4 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: winx64intel_perf_bisect Benchmark : v8.runtimestats.browsing_desktop Metric : total:500ms_window:renderer_eqt:v8:gc:full-mark-compactor_max/total:500ms_window:renderer_eqt:v8:gc:full-mark-compactor_max 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 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/8975071420013094768 For feedback, file a bug with component Speed>Bisection
,
Jul 5 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: winx64ati_perf_bisect Benchmark : v8.runtimestats.browsing_desktop Metric : total:500ms_window:renderer_eqt:v8:gc_max/total:500ms_window:renderer_eqt:v8:gc_max 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 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/8974980822404684400 For feedback, file a bug with component Speed>Bisection
,
Jul 7 2017
Given the high correlation with the ref graphs, this seems to be a bot issue that temporarily caused too low measurements. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by bmeu...@chromium.org
, Jul 2 2017