New issue
Advanced search Search tips

Issue 611151 link

Starred by 0 users

Issue metadata

Status: Fixed
Merged: issue 611039
Owner:
Closed: May 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

5.6% regression in thread_times.key_silk_cases at 392627:392652

Project Member Reported by tdres...@chromium.org, May 11 2016

Issue description

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

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


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

android-nexus6
Project Member

Comment 2 by 42576172...@developer.gserviceaccount.com, May 11 2016

Cc: wangxianzhu@chromium.org
Owner: wangxianzhu@chromium.org

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

Hi wangxianzhu@chromium.org, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


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


===== SUSPECTED CL(s) =====
Subject : Don't include contents visual overflow into paint invalidation rect
Author  : wangxianzhu
Commit description:
  
Now we always invalidate any object needing repaint, so we never need
the paint invalidation rect of an ancestor to cover descendants.

BUG= 436198 

Review-Url: https://codereview.chromium.org/1929413002
Cr-Commit-Position: refs/heads/master@{#392652}
Commit  : 638c1a24dc8fdcceb5b5f4acd9d03d3a09b9cfa3
Date    : Tue May 10 18:23:15 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev    N  Good?
chromium@392626  4.91415  0.0238053  5  good
chromium@392639  4.97816  0.0409124  5  good
chromium@392646  4.98722  0.0565869  5  good
chromium@392649  4.95491  0.0377102  5  good
chromium@392651  5.00458  0.0535484  5  good
chromium@392652  5.20134  0.0481354  5  bad    <--

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 611151

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests thread_times.key_silk_cases
Test Metric: thread_GPU_cpu_time_per_frame/thread_GPU_cpu_time_per_frame
Relative Change: 5.84%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2184
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9012932763869274496


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

| 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!
Mergedinto: 611039
Status: Duplicate (was: Assigned)
Status: Fixed (was: Duplicate)
Performance has restored to the original level.

Sign in to add a comment