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

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

8.1%-59.1% improvement in memory.long_running_idle_gmail_tbmv2 at 514517:514694

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

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


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

android-nexus7v2
chromium-rel-mac-retina
chromium-rel-mac11
chromium-rel-mac11-pro
chromium-rel-mac12
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
chromium-rel-win7-x64-dual
chromium-rel-win8-dual
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: winx64nvidia_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       : 2.61% | 260467382.167 -> 253661316.833

Revision                           Result                     N
chromium@514531                    260467382 +- 5394972       6      good
chromium@514597                    261569118 +- 6827465       6      good
chromium@514630                    262179094 +- 5470856       6      good
chromium@514639                    263577444 +- 4369883       5      good
chromium@514641                    262141575 +- 1062646       6      good
chromium@514641,v8@67d543ec31      261769061 +- 2516752       6      good
chromium@514641,v8@6bb1d47e6e      254431936 +- 1389248       6      bad       <--
chromium@514641,v8@ac0661b358      251733588 +- 16216998      6      bad
chromium@514641,v8@80cb266c75      253802996 +- 3116254       6      bad
chromium@514642                    253231141 +- 8294101       6      bad
chromium@514643                    251299176 +- 13517913      6      bad
chromium@514647                    252956116 +- 4344524       6      bad
chromium@514663                    253661317 +- 6569875       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/8963319730873747552


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment