New issue
Advanced search Search tips

Issue 781155 link

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



Sign in to add a comment

1%-33% regression in system_health.memory_desktop at 511552:512022

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

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 3 2017 

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

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


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

chromium-rel-mac-retina
chromium-rel-mac11
chromium-rel-mac11-pro
chromium-rel-mac12
chromium-rel-win7-dual
chromium-rel-win7-x64-dual
chromium-rel-win8-dual
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Nov 3 2017 


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

Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : v8-gc-incremental-finalize_sum/browse_media/browse_media_flickr_infinite_scroll

Revision             Result                    N
chromium@511658      0.8335 +- 0.026163        2      good
chromium@511884      0.92225 +- 0.0853742      4      bad

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=browse.media.flickr.infinite.scroll v8.browsing_desktop

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

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


For feedback, file a bug with component Speed>Bisection

Comment 4 by mlippautz@chromium.org, Nov 3 2017

Cc: -mlippautz@google.com mlippautz@chromium.org
Project Member

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


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

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/load_media/load_media_dailymotion

Revision             Result                   N
chromium@511700      23207546 +- 1568697      21      good
chromium@511850      23332376 +- 1757585      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 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.media.dailymotion 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/8963943166848919360


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

Comment 8 by 42576172...@developer.gserviceaccount.com, Nov 4 2017

Mergedinto: 779475
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Alex Moshchuk
  Commit : 9cf0ac139cc65890b9e036f704040c8da332d6e3
  Date   : Wed Oct 25 21:26:19 2017
  Subject: Add field trial testing config for sign-in process isolation.

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/load_media/load_media_dailymotion
  Change       : 25.65% | 19197952.0 -> 24122709.3333

Revision             Result                   N
chromium@510500      19197952 +- 642119       6      good
chromium@511250      19468288 +- 0.0          6      good
chromium@511438      19210240 +- 642119       6      good
chromium@511532      19210240 +- 642119       6      good
chromium@511579      19122859 +- 605396       6      good
chromium@511591      19035477 +- 478607       6      good
chromium@511593      19297621 +- 1048576      9      good
chromium@511594      22858411 +- 4261919      9      bad       <--
chromium@511597      22953984 +- 642119       6      bad
chromium@511602      22858411 +- 4261919      9      bad
chromium@511625      23390891 +- 957215       6      bad
chromium@512000      24122709 +- 3682478      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 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.media.dailymotion 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/8963922140812348256


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

Sign in to add a comment