New issue
Advanced search Search tips

Issue 610818 link

Starred by 0 users

Issue metadata

Status: Duplicate
Merged: issue 609765
Owner:
Closed: May 2016
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

21.1% regression in smoothness.gpu_rasterization.tough_filters_cases at 391721:391778

Project Member Reported by sullivan@chromium.org, May 10 2016

Issue description

Splitting off from  bug 609941  because of a different root cause.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=610818

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


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

android-galaxy-s5
Project Member

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

Mergedinto: 609765
Status: Duplicate (was: Assigned)

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


===== SUSPECTED CL(s) =====
Subject : cc: optimize filter backing store texture allocation.
Author  : senorblanco
Commit description:
  
The backing store used for filters in cc is determined by the
primitive bounds, and the filter outsets. This means that
we may end up allocating many textures of different sizes,
defeating Skia's texture cache. Texture allocation can be
slow, so we can ameliorate the allocation pressure by
rounding width and height up to the nearest power of 2.
(This is what Skia does internally for scratch textures).

BUG= 602785 
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel

Review-Url: https://codereview.chromium.org/1884553003
Cr-Commit-Position: refs/heads/master@{#391753}
Commit  : d47a9ef38a0c81f0250e575f08fb47fb56fe1d66
Date    : Thu May 05 04:29:08 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@391720  684.534  31.1954  5  good
chromium@391749  663.43   7.54266  5  good
chromium@391751  659.467  12.6808  5  good
chromium@391752  663.907  7.24236  5  good
chromium@391753  800.625  49.5843  5  bad    <--
chromium@391757  781.481  41.0399  5  bad
chromium@391764  776.247  45.4567  5  bad
chromium@391778  804.357  87.9775  5  bad

Bisect job ran on: android_s5_perf_bisect
Bug ID: 610818

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.gpu_rasterization.tough_filters_cases
Test Metric: frame_times/http___rawgit.com_WebKit_webkit_master_PerformanceTests_Animometer_developer.html?test-interval_20_display_minimal_controller_fixed_frame-rate_50_kalman-process-error_1_kalman-measurement-error_4_time-measurement_performance_suite-name_Animometer_test-name_Focus_complexity_100
Relative Change: 17.50%
Score: 99.5

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/655
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9013018643405307024


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

| 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