New issue
Advanced search Search tips

Issue 748448 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

1098.2% regression in system_health.memory_mobile at 488645:488797

Project Member Reported by hjd@google.com, Jul 25 2017

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jul 25 2017

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=748448

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


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

android-webview-nexus6
Project Member

Comment 3 by sheriffbot@chromium.org, Jul 25 2017

Labels: Hotlist-Google
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Jul 26 2017


=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:skia:effective_size_avg/load_tools/load_tools_weather
  Change       : 0.65% | 271380.0 -> 273356.0

Suspected Commit Range
  3 commits in range
  https://chromium.googlesource.com/chromium/src/+log/1d90c8175b1f4057e0e38afca54eeb65f0e2b25c..6d47bae2c9489a8b078cefd2ee072c49e5fe4f03


Revision             Result                  N
chromium@488644      271380 +- 0.0           14       good
chromium@488647      271380 +- 0.0           14       good
chromium@488648      ---                     ---      build failure
chromium@488649      ---                     ---      build failure
chromium@488650      914483 +- 5879047       14       bad
chromium@488654      914201 +- 5879478       14       bad
chromium@488664      1270445 +- 5600902      9        bad
chromium@488683      273356 +- 4840.19       6        bad
chromium@488721      486981 +- 4381854       21       bad
chromium@488797      273356 +- 7393.51       14       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.tools.weather 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/8973105170953979424


For feedback, file a bug with component Speed>Bisection
Status: WontFix (was: Untriaged)
This metric seems to have recovered.

Sign in to add a comment