Issue metadata
Sign in to add a comment
|
51.5% regression in v8.browsing_mobile at 489459:489543 |
||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 14 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8971270327614343040
,
Aug 14 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_webview_nexus6_aosp_perf_bisect Benchmark : v8.browsing_mobile Metric : v8-gc-total_max/browse_shopping/browse_shopping_lazada Revision Result N chromium@489458 40.7669 +- 13.6648 21 good chromium@489543 41.081 +- 10.5088 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.shopping.lazada v8.browsing_mobile More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8971270327614343040 For feedback, file a bug with component Speed>Bisection
,
Aug 21 2017
Not reproducible. |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 4 2017