Issue metadata
Sign in to add a comment
|
1.1%-2.8% regression in system_health.memory_mobile at 1531856634:1531962480 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 25
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8940070954805740000
,
Jul 25
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: go-webview-phone-perf-bisect Benchmark : system_health.memory_mobile Metric : memory:webview:all_processes:reported_by_os:system_memory:private_footprint_size_avg/load_news/load_news_washingtonpost Change : 0.06% | 42297636.5714 -> 42321432.381 Revision Result N android-chrome@e89c81435e 42297637 +- 487194 21 good android-chrome@029430f630 42321432 +- 522876 21 bad Please refer to the following doc on diagnosing memory regressions: https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md 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=load.news.washingtonpost system_health.memory_mobile More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8940070954805740000 For feedback, file a bug with component Speed>Bisection
,
Jul 25
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8940027312077779472
,
Jul 25
=== Auto-CCing suspected CL author sigurds@chromium.org === Hi sigurds@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 : Sigurd Schneider Commit : 46a78fbedfcd458f5d35097bdf1a9947644f4b0e Date : Tue Jul 17 15:33:20 2018 Subject: Revert "[embedded-builtins] Enable on all arches except x86 for benchmarks" Bisect Details Configuration: go-phone-512-perf-bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_os:system_memory:private_footprint_size_avg/load_media/load_media_facebook_photos Change : 1.36% | 46658901.3333 -> 47292416.0 Revision Result N android-chrome@99b6fd7dae 46658901 +- 403295 9 good android-chrome@6d62ea7763 46662542 +- 354965 9 good android-chrome@e5eafcf94f 46564693 +- 206816 6 good android-chrome@74662f91c8 46568789 +- 198674 6 good android-chrome@74662f91c8,chromium@575926 46597916 +- 265033 9 good android-chrome@74662f91c8,chromium@575929 46274560 +- 346423 6 good android-chrome@74662f91c8,chromium@575929,v8@46a78fbedf 46954496 +- 158315 6 bad <-- android-chrome@74662f91c8,chromium@575929,v8@e3a5b1e402 47056213 +- 191869 6 bad android-chrome@74662f91c8,chromium@575929,v8@16af1baac4 47068501 +- 228829 6 bad android-chrome@74662f91c8,chromium@575930 47058944 +- 470052 6 bad android-chrome@74662f91c8,chromium@575931 47190699 +- 213046 6 bad android-chrome@74662f91c8,chromium@575935 47026631 +- 222982 9 bad android-chrome@1032e70048 47037294 +- 247312 14 bad android-chrome@478583399d 47046949 +- 223722 14 bad android-chrome@029430f630 47292416 +- 432598 9 bad Please refer to the following doc on diagnosing memory regressions: https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md To Run This Test src/tools/perf/run_benchmark -v --browser=android-chrome --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.media.facebook.photos system_health.memory_mobile More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8940027312077779472 For feedback, file a bug with component Speed>Bisection
,
Jul 26
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jul 25