Issue metadata
Sign in to add a comment
|
3.7%-242.9% regression in system_health.common_desktop at 512426:512461 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Oct 31 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8964186959838947520
,
Oct 31 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: mac_10_12_perf_bisect Benchmark : system_health.common_desktop Metric : total:500ms_window:renderer_eqt_max/browse_search/browse_search_google_india Revision Result N chromium@512433 124.689 +- 233.517 21 good chromium@512453 125.314 +- 259.124 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.search.google.india system_health.common_desktop More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8964186959838947520 For feedback, file a bug with component Speed>Bisection
,
Jan 11 2018
๐ Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/1488fc77040000
,
Jan 11 2018
Most of these look like a return to previous levels, but kicked off one more bisect on a sustained eqt regression.
,
Jan 11 2018
๐ Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/1488fc77040000 Added missing well-known conflicting language codes. By napper@chromium.org ยท Mon Oct 30 00:51:36 2017 chromium @ 1ed2ebd683e0f3cd16c5b9e0fe182eafa577b75c Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Mar 21 2018
Patch reverted: https://chromium-review.googlesource.com/c/chromium/src/+/969681
,
Mar 21 2018
,
Mar 26 2018
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Oct 31 2017