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

Issue 783637 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

9.3%-52.7% improvement in memory.long_running_idle_gmail_tbmv2 at 514597:514726

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=783637

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


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

chromium-rel-win8-dual
win-high-dpi
Project Member

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

Mergedinto: 783622
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Ulan Degenbaev
  Commit : 6bb1d47e6e82f75ead36cdab209afc5dafa8329c
  Date   : Tue Nov 07 13:11:10 2017
  Subject: [heap] Re-enable concurrent marking.

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : memory.long_running_idle_gmail_tbmv2
  Metric       : memory:chrome:renderer_processes:reported_by_os:system_memory:proportional_resident_size_max/memory:chrome:renderer_processes:reported_by_os:system_memory:proportional_resident_size_max
  Change       : 9.60% | 254064603.667 -> 229680496.0

Revision                           Result                     N
chromium@514596                    254064604 +- 3933591       6      good
chromium@514629                    252554914 +- 2817442       6      good
chromium@514637                    252831848 +- 6246140       9      good
chromium@514641                    246125504 +- 62708814      9      good
chromium@514641,v8@67d543ec31      253885154 +- 3991826       6      good
chromium@514641,v8@6bb1d47e6e      229940836 +- 2820585       6      bad       <--
chromium@514641,v8@ac0661b358      229463255 +- 4260672       6      bad
chromium@514641,v8@80cb266c75      229535172 +- 6103147       9      bad
chromium@514642                    228830558 +- 6922642       9      bad
chromium@514643                    229653623 +- 4123824       9      bad
chromium@514645                    229861379 +- 7051479       9      bad
chromium@514661                    231257030 +- 3286232       6      bad
chromium@514726                    229680496 +- 8088429       6      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 memory.long_running_idle_gmail_tbmv2

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

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


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment