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

Issue 783686 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

12.2%-83.7% improvement in memory.long_running_idle_gmail_background_tbmv2 at 514532: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=783686

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


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

chromium-rel-win7-gpu-intel
chromium-rel-win7-x64-dual
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_background_tbmv2
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:effective_size_max/memory:chrome:renderer_processes:reported_by_chrome:v8:effective_size_max
  Change       : 10.19% | 138291882.667 -> 124204373.333

Revision                           Result                     N
chromium@514596                    138291883 +- 9889045       6      good
chromium@514629                    138789547 +- 10156554      6      good
chromium@514637                    136631637 +- 9488304       6      good
chromium@514641                    137539584 +- 10186580      6      good
chromium@514641,v8@67d543ec31      136221355 +- 6413074       6      good
chromium@514641,v8@6bb1d47e6e      124379136 +- 2774271       6      bad       <--
chromium@514641,v8@ac0661b358      123263659 +- 1428719       6      bad
chromium@514641,v8@80cb266c75      125777237 +- 6492145       6      bad
chromium@514642                    124265131 +- 3146946       6      bad
chromium@514643                    124816043 +- 3952496       6      bad
chromium@514645                    124661760 +- 4751215       6      bad
chromium@514661                    125515093 +- 4941490       6      bad
chromium@514726                    124204373 +- 2305278       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_background_tbmv2

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

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


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment