Issue metadata
Sign in to add a comment
|
3.3%-4.5% regression in speedometer at 500441:500556 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Sep 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8968763157805818368
,
Sep 11 2017
=== Auto-CCing suspected CL author mgiuca@chromium.org === Hi mgiuca@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 : Matt Giuca Commit : 16a22949c41721a9a8b80aa3a0c801dfb54b6bb8 Date : Fri Sep 08 05:05:40 2017 Subject: Revert "BlinkGC: Cleanup heap counters" Bisect Details Configuration: winx64_high_dpi_perf_bisect Benchmark : speedometer Metric : AngularJS-TodoMVC/AngularJS-TodoMVC Change : 3.10% | 670.117285714 -> 649.3255 Revision Result N chromium@500507 670.117 +- 79.2167 21 good chromium@500509 676.275 +- 55.2248 6 good chromium@500510 680.418 +- 41.7372 6 good chromium@500511 647.562 +- 7.06983 6 bad <-- chromium@500514 642.273 +- 64.7875 14 bad chromium@500520 652.099 +- 87.0006 20 bad chromium@500532 642.142 +- 24.8387 14 bad chromium@500556 649.326 +- 89.354 20 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 speedometer More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8968763157805818368 For feedback, file a bug with component Speed>Bisection
,
Sep 12 2017
This was a revert I made during sheriffing (presumably of a performance improvement). Assigning to keishi to re-land r500487 if not already done. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Sep 11 2017