New issue
Advanced search Search tips

Issue 635027 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner:
Closed: Aug 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.8%-6% regression in smoothness.tough_path_rendering_cases at 409237:409321

Project Member Reported by sullivan@chromium.org, Aug 5 2016

Issue description

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

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


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

chromium-rel-mac-retina
chromium-rel-win7-gpu-ati
Labels: Performance-Sheriff
Mergedinto: 633843
Status: Duplicate (was: Assigned)

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


===== SUSPECTED CL(s) =====
Subject : Raster display item lists via a visual rect RTree.
Author  : wkorman
Commit description:
  
Rather than caching and playing back an entire SkPicture
when rastering a display item list for a particular
playback rect, instead retain display items and query
them via an RTree of their visual rects to find and
raster only what's needed.

Display item lists no longer support the notion of a
bounding "layer rect" with mutable origin.

DisplayItemListSettings proto is obsolete after this
change as it's comprised solely of one field to allow
switching whether to use the aforementioned now-deleted
cached SkPicture code path. It will be deleted in a
subsequent patch.

BUG= 529938 
TBR=sadrul
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_precise_blink_rel

Review-Url: https://codereview.chromium.org/1484163002
Cr-Commit-Position: refs/heads/master@{#409291}
Commit  : ccb9e13712b1632b889960d1d85d556c0139fd51
Date    : Tue Aug 02 20:08:52 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev    N  Good?
chromium@409282  31.1551  0.150662   5  good
chromium@409290  31.1388  0.182684   5  good
chromium@409291  32.3356  0.316151   5  bad    <--
chromium@409292  32.3312  0.191911   5  bad
chromium@409294  32.2845  0.169791   5  bad
chromium@409298  32.3134  0.1867     5  bad
chromium@409309  32.2654  0.0904796  5  bad

Bisect job ran on: winx64ati_perf_bisect
Bug ID: 635027

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.gpu_rasterization.tough_path_rendering_cases
Test Metric: frame_times/frame_times
Relative Change: 3.56%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64ati_perf_bisect/builds/1492
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005142134335400064


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

| 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