Issue metadata
Sign in to add a comment
|
8.3%-2675.3% regression in v8.runtimestats.browsing_mobile at 489897:490039 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 3 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8972283117432907696
,
Aug 3 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Helen Li Commit : 73f7cac54a1108eac07d5c7c3367f979a899a0bd Date : Thu Jul 27 14:57:57 2017 Subject: [wpr-go] Switch system_health_mobile.json to use go Bisect Details Configuration: android_webview_arm64_aosp_perf_bisect Benchmark : v8.runtimestats.browsing_mobile Metric : Optimize:duration_avg/browse_news/browse_news_cricbuzz Change : 2540.07% | 0.463333333333 -> 12.2323333333 Revision Result N chromium@489896 0.463333 +- 0.404615 6 good chromium@489919 0.391 +- 0.248177 6 good chromium@489922 0.372 +- 0.0699571 6 good chromium@489923 12.7968 +- 2.67143 6 bad <-- chromium@489924 13.5875 +- 1.6496 6 bad chromium@489925 11.0987 +- 3.29302 6 bad chromium@489931 12.1053 +- 1.81478 6 bad chromium@489942 12.2323 +- 3.39475 6 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.news.cricbuzz v8.runtimestats.browsing_mobile More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8972283117432907696 For feedback, file a bug with component Speed>Bisection
,
Aug 3 2017
+ ulan, cbruni@: What does v8.runtimestats.browsing_mobile measure? Could you take a look at this alert? Do the graphs look reasonable?
,
Aug 11 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 3 2017