New issue
Advanced search Search tips

Issue 747266 link

Starred by 1 user
Status: Duplicate
Merged: issue 745159
Owner: ----
Closed: Jul 2017
Cc:
mlippautz@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2.2%-42.7% regression in system_health.memory_desktop at 477411:486045

Project Member Reported by mlippautz@chromium.org, Jul 21 2017 
See the link to graphs below.
Project Member

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

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

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


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

chromium-rel-mac11
linux-release
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jul 22 2017 


=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/load_tools/load_tools_weather


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=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.tools.weather system_health.memory_desktop

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8973475262594662416


For feedback, file a bug with component Speed>Bisection
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Jul 24 2017

Mergedinto: 745159
Status: Duplicate (was: Untriaged)

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Ken Rockot
  Commit : 474df01407e5d38c85364ae4d1709b8d9af16f16
  Date   : Wed Jul 12 13:28:56 2017
  Subject: Mojo C++ Bindings: Lazy Serialization

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/load_chrome/load_chrome_blank
  Change       : 2.28% | 10304548.1667 -> 10539311.0

Revision             Result                   N
chromium@485903      10304548 +- 36287.8      6      good
chromium@485920      10299789 +- 59907.6      6      good
chromium@485929      10300357 +- 49107.1      6      good
chromium@485933      10238810 +- 315817       6      good
chromium@485934      10301903 +- 76589.1      6      good
chromium@485935      10537006 +- 54129.7      6      bad       <--
chromium@485937      10534079 +- 64191.3      6      bad
chromium@485970      10539311 +- 65903.9      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=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.chrome.blank system_health.memory_desktop

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8973178457133791952


For feedback, file a bug with component Speed>Bisection
►

Sign in to add a comment