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

Issue 604401 link

Starred by 0 users

Issue metadata

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



Sign in to add a comment

15.3%-250.2% regression in thread_times.simple_mobile_sites at 385442:387424

Project Member Reported by rsch...@chromium.org, Apr 18 2016

Issue description

See the link to graphs below.
 
Project Member

Comment 2 by 42576172...@developer.gserviceaccount.com, Apr 18 2016

Mergedinto: 601793
Status: Duplicate (was: Assigned)

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


===== SUSPECTED CL(s) =====
Subject : Revert of Enable GPU Rasterization for content with any author defined viewport. (patchset #2 id:20001 of https://codereview.chromium.org/1817583003/ )
Author  : vmiura
Commit description:
  
Reason for revert:
Reverting until we can debug memory health regressions on WebView.

BUG= 596881 

Original issue's description:
> Enable GPU Rasterization for content with any author defined viewport.
>
> BUG= 591179 
>
> Committed: https://crrev.com/b338ee0b3125007b94854e44ed7b6df820c72a75
> Cr-Commit-Position: refs/heads/master@{#382394}

TBR=aelias@chromium.org,pdr@chromium.org,chrishtr@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG= 591179 

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

Cr-Commit-Position: refs/heads/master@{#385547}
Commit  : e707452627a8ace7951e49421be443fe544aac71
Date    : Wed Apr 06 20:29:10 2016


===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@385441         0.389194    0.018838    5           good
chromium@385503         0.394389    0.02607     5           good
chromium@385534         0.372082    0.01507     5           good
chromium@385542         0.394708    0.02396     5           good
chromium@385546         0.376331    0.012247    5           good
chromium@385547         1.402193    0.067703    5           bad         <-
chromium@385548         1.397731    0.051358    5           bad
chromium@385550         1.415671    0.035951    5           bad
chromium@385565         1.453196    0.062819    5           bad
chromium@385689         1.444792    0.040745    5           bad
chromium@385937         1.453285    0.042277    5           bad
chromium@386433         2.368285    0.050997    5           bad
chromium@387424         1.413087    0.053326    5           bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 604401

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

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/1742
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9015027800408729520


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

| 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