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

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


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

android-nexus5X

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9004218535531855824

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


===== SUSPECTED CL(s) =====
Subject : Reland "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.

Last reverted change: http://crrev.com/2217263003

BUG= 529938 
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_precise_blink_rel
TBR=chrishtr,vmpstr

Review-Url: https://codereview.chromium.org/2225563002
Cr-Commit-Position: refs/heads/master@{#411560}
Commit  : 971a9c9725e293bd89b7cb1475acdc502065e6b3
Date    : Fri Aug 12 05:55:13 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev    N  Good?
chromium@411524  2.16777  0.0348115  5  good
chromium@411544  2.13605  0.0146008  5  good
chromium@411554  2.15941  0.0134125  5  good
chromium@411559  2.17209  0.025065   5  good
chromium@411560  2.27748  0.0267367  5  bad    <--
chromium@411561  2.2878   0.0217994  5  bad
chromium@411563  2.27096  0.0366724  5  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 638036

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

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/522
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004218535531855824


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

| 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!