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

Issue 638999 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner:
Last visit > 30 days ago
Closed: Aug 2016
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

38.3% regression in system_health.memory_desktop at 409261:409309

Project Member Reported by petrcermak@chromium.org, Aug 18 2016

Issue description

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

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


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

chromium-rel-mac-retina
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Aug 19 2016

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@409260  56436237  7327.15  5  good
chromium@409285  56439514  8973.89  5  good
chromium@409288  56439514  8973.89  5  good
chromium@409290  60047270  8063530  5  good
chromium@409291  78063117  7327.15  5  bad    <--
chromium@409297  81674150  8063530  5  bad
chromium@409309  81667597  8067189  5  bad

Bisect job ran on: mac_retina_perf_bisect
Bug ID: 638999

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_desktop
Test Metric: load_tools-memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/load_tools_docs
Relative Change: 44.71%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1587
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9003969450543591168


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

| 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!
Labels: SystemHealth-Sheriff

Sign in to add a comment