New issue
Advanced search Search tips

Issue 648913 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

10.3% regression in blink_perf.svg at 419612:419653

Project Member Reported by toyoshim@chromium.org, Sep 21 2016

Issue description

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

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


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

chromium-rel-win7-x64-dual
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Sep 21 2016

Mergedinto: 648907
Status: Duplicate (was: Assigned)

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


===== SUSPECTED CL(s) =====
Subject : cc: Remove estimated parent draw time from renderer
Author  : enne
Commit description:
  
This is a display scheduler only concept now that unified begin frame is
turned on.  Renderers can just use the deadline passed to them from the
top level begin frame source.

This fixes a regression from https://codereview.chromium.org/2299003002
where Android was using the incorrect parent estimated draw time of
none and so thought it had less time for frames than it did.

R=brianderson@chromium.org
BUG= 646377 
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_precise_blink_rel

Review-Url: https://codereview.chromium.org/2352823002
Cr-Commit-Position: refs/heads/master@{#419617}
Commit  : bfdea7f114aded7866981b8bfe3edd0c75155f12
Date    : Tue Sep 20 01:11:26 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@419611  248.34   3.28688  5  good
chromium@419614  247.479  1.21675  5  good
chromium@419616  248.372  3.9694   5  good
chromium@419617  277.788  6.52722  5  bad    <--
chromium@419622  276.348  6.29028  5  bad
chromium@419632  276.061  5.20483  5  bad
chromium@419653  272.03   4.81223  5  bad

Bisect job ran on: win_x64_perf_bisect
Bug ID: 648913

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.svg
Test Metric: Cowboy_transform/Cowboy_transform
Relative Change: 9.54%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_x64_perf_bisect/builds/1476
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9000920493671694736


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

| 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