New issue
Advanced search Search tips

Issue 597649 link

Starred by 0 users

Issue metadata

Status: Fixed
Owner:
Closed: Apr 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

15.2%-17.6% regression in blink_perf.canvas at 382796:382801

Project Member Reported by mustaq@chromium.org, Mar 24 2016

Issue description

See the link to graphs below.
 

Comment 1 by mustaq@chromium.org, Mar 24 2016

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

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


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

chromium-rel-mac-hdd
chromium-rel-mac10
Project Member

Comment 2 by 42576172...@developer.gserviceaccount.com, Mar 30 2016

Cc: ccameron@chromium.org
Owner: ccameron@chromium.org

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

Hi ccameron@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 : Mac: Decode hardware to 420 instead of 422
Author  : ccameron
Commit description:
  
If the decoded frame is going to be used as a CALayer overlay, then
it will never be converted to RGBA. If it is used by OpenGL, then the
same infrastructure for software frames will be employed to make an
expensive RGBA copy of the frame.

BUG= 594452 

Review URL: https://codereview.chromium.org/1822173002

Cr-Commit-Position: refs/heads/master@{#382797}
Commit  : 24da601d444c8822c5ff0a10751b9384f25dd1b4
Date    : Wed Mar 23 06:13:40 2016


===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@382795         2983.632627 35.874495   5           good
chromium@382796         2943.049353 60.490482   5           good
chromium@382797         2494.053495 14.985538   5           bad         <-

Bisect job ran on: mac_10_10_perf_bisect
Bug ID: 597649

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --also-run-disabled-tests blink_perf.canvas
Test Metric: upload-video-to-texture/upload-video-to-texture
Relative Change: 16.41%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_10_perf_bisect/builds/2070
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9016732549775546432


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

| 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!
This CL has been reverted, but it's coming back in. This is an expected regression -- we are intentionally making video canvas rendering higher power in exchange for making video playback lower power.
Status: Fixed (was: Assigned)

Sign in to add a comment