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

Issue 766582 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Nov 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

15.1%-37.4% regression in blink_perf.dom at 502396:502482

Project Member Reported by alexclarke@chromium.org, Sep 19 2017

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Sep 19 2017

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

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


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

chromium-rel-win7-x64-dual
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Sep 19 2017

Cc: u...@chromium.org
Owner: u...@chromium.org
Status: Assigned (was: Untriaged)

=== Auto-CCing suspected CL author ulan@chromium.org ===

Hi ulan@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : Ulan Degenbaev
  Commit : 8d1ad4b8aad07c2bb3d904e10efbe75f17236298
  Date   : Fri Sep 15 11:08:16 2017
  Subject: [heap] Remove adhoc weakness in TransitionArray.

Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : blink_perf.dom
  Metric       : modify-element-title/modify-element-title
  Change       : 35.16% | 101.379833333 -> 137.027333333

Revision                           Result                   N
chromium@502395                    101.38 +- 5.55843        6      good
chromium@502439                    98.403 +- 2.43142        6      good
chromium@502461                    97.5428 +- 2.27251       6      good
chromium@502467                    97.1988 +- 0.632824      6      good
chromium@502470                    97.8263 +- 3.7977        6      good
chromium@502470,v8@70372dfc64      96.7477 +- 3.85079       6      good
chromium@502470,v8@a10e4a179e      100.468 +- 3.09451       6      good
chromium@502470,v8@c87f8954cc      99.6467 +- 0.947994      6      good
chromium@502470,v8@8d1ad4b8aa      138.132 +- 3.71602       6      bad       <--
chromium@502470,v8@dbd3d58ffc      138.111 +- 4.55336       6      bad
chromium@502471                    136.582 +- 2.59257       6      bad
chromium@502472                    138.716 +- 3.01904       6      bad
chromium@502482                    137.027 +- 2.04634       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 blink_perf.dom

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

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


For feedback, file a bug with component Speed>Bisection

Comment 4 by u...@chromium.org, Nov 21 2017

Status: WontFix (was: Assigned)
The graph recovered.

Sign in to add a comment