New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 738875 link

Starred by 1 user
Status: Duplicate
Merged: issue 737353
Owner: ----
Closed: Jul 2017
Cc:
█ perezju@google.com
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3% regression in system_health.memory_desktop at 482373:482485

Project Member Reported by perezju@google.com, Jul 3 2017 
See the link to graphs below.
Project Member

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


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/load_search/load_search_taobao

Revision             Result                    N
chromium@482372      189618858 +- 6297928      21      good
chromium@482485      189838057 +- 5039044      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=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.search.taobao 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/8975086933982037728


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

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


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/load_search/load_search_taobao

Revision             Result                     N
chromium@482372      192339363 +- 27839590      21      good
chromium@482485      194065417 +- 3738568       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=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.search.taobao 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/8975078969463054736


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

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

Mergedinto: 737353
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : perezju
  Commit : b4eb70c319cb0f38d1a7764e7d9fb56dc96f8bcf
  Date   : Mon Jun 26 14:25:41 2017
  Subject: [System Health] Extend dump time to 5 seconds

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/load_search/load_search_taobao
  Change       : 2.00% | 91466816.3571 -> 92835713.1667

Revision                                 Result                    N
chromium@482229                          91466816 +- 3993759       14      good
chromium@482261                          89496951 +- 18621378      9       good
chromium@482277                          91575234 +- 1904994       14      good
chromium@482281                          91452045 +- 1435547       9       good
chromium@482282                          91308248 +- 1733130       6       good
chromium@482282,catapult@b4eb70c319      92704353 +- 1482230       6       bad       <--
chromium@482283                          92725579 +- 1910870       9       bad
chromium@482285                          92898770 +- 807530        6       bad
chromium@482293                          91176566 +- 20278167      14      bad
chromium@482357                          92696391 +- 1459122       9       bad
chromium@482485                          92835713 +- 1792344       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.search.taobao 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/8975077238443478256


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

Sign in to add a comment