New issue
Advanced search Search tips

Issue 739877 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner:
Closed: Jul 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.2%-5.2% regression in system_health.memory_mobile at 484234:484270

Project Member Reported by mustaq@chromium.org, Jul 6 2017

Issue description

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

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


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

android-webview-nexus5X
Cc: perezju@chromium.org
Owner: perezju@chromium.org

=== Auto-CCing suspected CL author perezju@chromium.org ===

Hi perezju@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 : perezju
  Commit : b5c1738572410f30cbcae23354f1738cf0b222ef
  Date   : Wed Jul 05 08:52:52 2017
  Subject: [Telemetry] Trigger GC on Chrome processes forked from Zygote

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/background_social/background_social_facebook
  Change       : 5.35% | 1562624.0 -> 1646250.66667

Revision                                 Result                  N
chromium@484233                          1562624 +- 0.0          6      good
chromium@484238                          1566037 +- 18695.6      6      good
chromium@484239                          1574229 +- 3739.12      6      good
chromium@484239,catapult@b5c1738572      1663317 +- 18695.6      6      bad       <--
chromium@484240                          1659051 +- 4673.9       6      bad
chromium@484241                          1649664 +- 0.0          6      bad
chromium@484243                          1649664 +- 28963.1      6      bad
chromium@484252                          1649664 +- 40960.0      6      bad
chromium@484270                          1646251 +- 34473.0      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-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=background.social.facebook 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/8974785902717145968


For feedback, file a bug with component Speed>Bisection
 Issue 739878  has been merged into this issue.
 Issue 739733  has been merged into this issue.
Status: WontFix (was: Untriaged)
These are expected, and already discussed at issue 724032.
Project Member

Comment 7 by 42576172...@developer.gserviceaccount.com, Jul 10 2017

 Issue 740125  has been merged into this issue.

Sign in to add a comment