New issue
Advanced search Search tips

Issue 781795 link

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



Sign in to add a comment

5.7%-153.6% regression in memory.long_running_idle_gmail_tbmv2 at 513606:513741

Project Member Reported by mustaq@chromium.org, Nov 6 2017 
See the link to graphs below.
Project Member

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

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

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


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

android-nexus5
android-nexus7v2
chromium-rel-mac-retina
chromium-rel-mac11
chromium-rel-mac11-pro
chromium-rel-mac12
chromium-rel-mac12-mini-8gb
chromium-rel-win10
chromium-rel-win7-dual
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
chromium-rel-win7-x64-dual
Project Member

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

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/14a26f7af80000
Project Member

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

Mergedinto: 781823
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Ulan Degenbaev
  Commit : 586067e45dd542a117b67ad66d3b14475d8d571f
  Date   : Thu Nov 02 19:10:00 2017
  Subject: Reland "[heap] Temporarily disable 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       : 10.46% | 228704215.5 -> 252634072.167

Revision                           Result                     N
chromium@513715                    228704216 +- 3573471       6      good
chromium@513718                    221273544 +- 45348899      6      good
chromium@513719                    228257385 +- 4880745       9      good
chromium@513719,v8@a274fc6536      229417754 +- 5983310       9      good
chromium@513719,v8@694a18781c      228084334 +- 5378663       9      good
chromium@513719,v8@586067e45d      245810683 +- 61787605      9      bad       <--
chromium@513720                    253118747 +- 3476607       6      bad
chromium@513721                    253690661 +- 3755857       6      bad
chromium@513727                    252675819 +- 3612954       6      bad
chromium@513739                    253401507 +- 1673044       6      bad
chromium@513762                    252634072 +- 3409764       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/8963658945438674928


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

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


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

Suspected Commit
  Author : Ulan Degenbaev
  Commit : 586067e45dd542a117b67ad66d3b14475d8d571f
  Date   : Thu Nov 02 19:10:00 2017
  Subject: Reland "[heap] Temporarily disable concurrent marking."

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : memory.long_running_idle_gmail_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       : 6.29% | 78376960.0 -> 83307178.6667

Revision                           Result                   N
chromium@513709                    78376960 +- 2673355      6      good
chromium@513717                    78289579 +- 1370523      6      good
chromium@513719                    77910926 +- 4157736      9      good
chromium@513719,v8@a274fc6536      78784740 +- 7103194      9      good
chromium@513719,v8@694a18781c      77590528 +- 3210595      6      good
chromium@513719,v8@586067e45d      83298987 +- 1048576      9      bad       <--
chromium@513720                    83219797 +- 478607       6      bad
chromium@513721                    83307179 +- 605396       6      bad
chromium@513725                    83477163 +- 597635       6      bad
chromium@513741                    83307179 +- 605396       6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --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/8963658969349906464


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

Sign in to add a comment