New issue
Advanced search Search tips

Issue 740127 link

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



Sign in to add a comment

17.3%-30.2% regression in system_health.memory_mobile at 484446:484491

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

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

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

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


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

android-nexus7v2
Project Member

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


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

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/background_news/background_news_nytimes

Revision             Result                    N
chromium@484445      17668584 +- 26795928      21      good
chromium@484491      16524434 +- 26477837      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=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=background.news.nytimes 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/8974716193762120704


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

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

Mergedinto: 740121
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Fady Samuel
  Commit : 28c5a8185d81adc5252e7280d5d0b652d998018f
  Date   : Thu Jul 06 00:10:04 2017
  Subject: Decouple cc::Surface from cc::CompositorFrameSinkSupport.

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/browse_shopping/browse_shopping_lazada
  Change       : 84.01% | 30201852.0 -> 55573714.6667

Revision             Result                    N
chromium@484295      30201852 +- 1758552       6      good
chromium@484346      30516498 +- 75713.7       6      good
chromium@484371      30516498 +- 75713.7       6      good
chromium@484375      29866599 +- 2252588       6      good
chromium@484376      30191549 +- 1747273       6      good
chromium@484377      57905085 +- 2031302       6      bad       <--
chromium@484378      58678736 +- 1929699       6      bad
chromium@484384      55816125 +- 12492789      6      bad
chromium@484396      58090770 +- 75713.7       6      bad
chromium@484497      55573715 +- 12635047      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-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.shopping.lazada 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/8974698080553284032


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

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


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

Suspected Commit
  Author : Fady Samuel
  Commit : 28c5a8185d81adc5252e7280d5d0b652d998018f
  Date   : Thu Jul 06 00:10:04 2017
  Subject: Decouple cc::Surface from cc::CompositorFrameSinkSupport.

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/browse_shopping/browse_shopping_amazon
  Change       : 182.14% | 34505888.0 -> 97354912.0

Revision             Result                    N
chromium@484295      34505888 +- 0.0           6      good
chromium@484346      33855989 +- 2251315       6      good
chromium@484371      33855989 +- 2251315       6      good
chromium@484375      33855989 +- 2251315       6      good
chromium@484376      33855989 +- 2251315       6      good
chromium@484377      98242379 +- 8875454       6      bad       <--
chromium@484378      93894287 +- 23616907      6      bad
chromium@484384      100041888 +- 6792507      6      bad
chromium@484396      95317835 +- 17889417      6      bad
chromium@484497      97354912 +- 9252479       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-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.shopping.amazon 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/8974698062590335344


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

Sign in to add a comment