New issue
Advanced search Search tips

Issue 865869 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 865870
Owner: ----
Closed: Jul 22
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.1%-28% regression in system_health.memory_mobile at 1531856634:1531962480

Project Member Reported by mlippautz@chromium.org, Jul 20

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=865869

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=f6575bb6bf62a9e9606b16a12f39f58c79f3066e62d3ea9c10a6b4700feae11d


Bot(s) for this bug's original alert(s):

health-plan-webview-phone
perf-go-phone-1024
perf-go-phone-512
perf-go-webview-phone
Mergedinto: 865870
Status: Duplicate (was: Untriaged)

=== 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-1024-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size_avg/browse_news/browse_news_qq
  Change       : 33.93% | 1388870.66667 -> 1860145.33333

Revision                                                     Result                 N
android-chrome@74662f91c8                                    1388871 +- 131360      9       good
android-chrome@74662f91c8,chromium@575926                    1430300 +- 169293      14      good
android-chrome@74662f91c8,chromium@575929                    1389289 +- 132199      9       good
android-chrome@74662f91c8,chromium@575929,v8@46a78fbedf      1816855 +- 175516      9       bad       <--
android-chrome@74662f91c8,chromium@575929,v8@e3a5b1e402      1860723 +- 198375      9       bad
android-chrome@74662f91c8,chromium@575929,v8@16af1baac4      1861028 +- 205615      6       bad
android-chrome@74662f91c8,chromium@575930                    1772363 +- 132815      9       bad
android-chrome@74662f91c8,chromium@575931                    1816419 +- 174936      9       bad
android-chrome@74662f91c8,chromium@575935                    1860636 +- 198574      9       bad
android-chrome@1032e70048                                    1816546 +- 174851      9       bad
android-chrome@4e67b217c5                                    1772277 +- 132192      9       bad
android-chrome@bdf6ddc146                                    1772374 +- 132655      9       bad
android-chrome@478583399d                                    1860145 +- 204405      6       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=browse.news.qq 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/8940499315766466816


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment