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

Issue 783722 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 783650
Owner: ----
Closed: Nov 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

6.2%-9.7% regression in system_health.memory_desktop at 515009:515101

Project Member Reported by alexclarke@chromium.org, Nov 10 2017

Issue description

See the link to graphs below.
 
Project Member

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

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

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


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

chromium-rel-win10
Project Member

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

Mergedinto: 783650
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Zhenyao Mo
  Commit : 1202f66559ca7e37f643a691cac72144ab60493f
  Date   : Thu Nov 09 00:45:05 2017
  Subject: [reland] Move GPU compositing blacklisting to GPU process.

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:proportional_resident_size_avg/load_news/load_news_bbc
  Change       : 7.39% | 122509395.5 -> 131567983.5

Revision             Result                    N
chromium@515008      122509396 +- 987944       6      good
chromium@515032      122448170 +- 1063700      6      good
chromium@515035      122549074 +- 990514       6      good
chromium@515036      131359589 +- 586896       6      bad       <--
chromium@515037      131448788 +- 925625       6      bad
chromium@515038      131450192 +- 1457532      6      bad
chromium@515044      131251655 +- 2072333      6      bad
chromium@515055      132867875 +- 2758007      6      bad
chromium@515101      131567984 +- 350350       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.news.bbc 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/8963317833504303408


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment