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

Issue 659060 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 659059
Owner: ----
Closed: Oct 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

13.6% regression in blink_perf.events at 426622:426697

Project Member Reported by alexclarke@chromium.org, Oct 25 2016

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=659060

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg3bLPrwoM


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

android-nexus9
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Oct 25 2016

Mergedinto: 659059
Status: Duplicate (was: Untriaged)

===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : Don't apply clips to children of composited-scrolling elements for overlap testing.
Author  : chrishtr
Commit description:
  
However, only compare these unclipped rects with other unclipped rects. This
prevents excessive layer explosion outside of the composited-scrolling layer.

This requires storing unclipped absolute rects for every PaintLayer.

BUG= 652448 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2

Review-Url: https://chromiumcodereview.appspot.com/2425873005
Cr-Commit-Position: refs/heads/master@{#426664}
Commit  : 0a78cbe13de10c5a1c951d753fd13d01c8b3488e
Date    : Fri Oct 21 00:56:33 2016


===== TESTED REVISIONS =====
Revision         Mean      Std Dev      N  Good?
chromium@426621  0.254427  0.0020048    5  good
chromium@426659  0.254445  0.000711349  5  good
chromium@426662  0.261006  0.00556259   5  good
chromium@426663  0.254203  0.00160762   5  good
chromium@426664  0.214251  0.0062531    5  bad    <--
chromium@426669  0.217277  0.00278937   5  bad
chromium@426678  0.215652  0.00320501   5  bad
chromium@426697  0.21565   0.0067873    5  bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 659060

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.events
Test Metric: hit-test-lots-of-layers/hit-test-lots-of-layers
Relative Change: 15.24%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/2211
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8997836125286258784


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5806730749935616

| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!

Sign in to add a comment