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

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

84.3% improvement in memory.long_running_idle_gmail_background_tbmv2 at 514532:514663

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

Issue description

Suspiciously large improvement, did something break?
 
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=783770

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


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

chromium-rel-win7-gpu-nvidia
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_background_tbmv2
  Metric       : v8-gc-latency-mark-compactor_max/v8-gc-latency-mark-compactor_max
  Change       : 81.57% | 69.5595 -> 13.4414444444

Revision                           Result                   N
chromium@514531                    69.5595 +- 32.8969       6       good
chromium@514597                    64.4488 +- 25.114        9       good
chromium@514630                    54.6071 +- 69.4982       14      good
chromium@514639                    67.001 +- 21.5375        6       good
chromium@514641                    65.9344 +- 19.8618       9       good
chromium@514641,v8@67d543ec31      66.6783 +- 21.2148       9       good
chromium@514641,v8@6bb1d47e6e      10.2937 +- 1.33353       6       bad       <--
chromium@514641,v8@ac0661b358      13.0337 +- 6.29463       6       bad
chromium@514641,v8@80cb266c75      23.3838 +- 75.5646       9       bad
chromium@514642                    11.4103 +- 4.44314       6       bad
chromium@514643                    10.5767 +- 0.771934      6       bad
chromium@514647                    11.5667 +- 3.81745       6       bad
chromium@514663                    13.4414 +- 7.85989       9       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/8963304450275177872


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment