New issue
Advanced search Search tips

Issue 784854 link

Starred by 1 user
Status: Duplicate
Merged: issue 783648
Owner: ----
Closed: Nov 2017
Cc:
tdres...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

11% regression in smoothness.gpu_rasterization.tough_path_rendering_cases at 515091:515122

Project Member Reported by tdres...@chromium.org, Nov 14 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 14 2017 

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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=5117e94b9c6e09d5f5b2b56fd26ff474fc6707617e2b4aa820fe0afeb1b1cb62


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

android-nexus6
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Nov 14 2017 


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : smoothness.gpu_rasterization.tough_path_rendering_cases
  Metric       : frame_times/GUIMark Vector Chart Test

Revision             Result                  N
chromium@515090      21.9668 +- 2.89941      21      good
chromium@515122      22.0619 +- 3.39339      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=GUIMark.Vector.Chart.Test smoothness.gpu_rasterization.tough_path_rendering_cases

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8962941184457794608


For feedback, file a bug with component Speed>Bisection
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Nov 15 2017

Mergedinto: 783648
Status: Duplicate (was: Untriaged)

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Justin Novosad
  Commit : 5b07996e178c5f4e153e771d48ab839867fa7440
  Date   : Wed Nov 08 23:26:00 2017
  Subject: Reland: Refactor of Canvas2DLayerBridge resource model

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : smoothness.gpu_rasterization.tough_path_rendering_cases
  Metric       : frame_times/GUIMark Vector Chart Test
  Change       : 11.77% | 20.4148420402 -> 22.5446744836

Revision             Result                   N
chromium@515000      20.4148 +- 1.6439        9      good
chromium@515001      22.5322 +- 1.1225        6      bad       <--
chromium@515002      23.2627 +- 1.52319       6      bad
chromium@515003      22.6729 +- 2.04556       6      bad
chromium@515005      22.434 +- 4.8886         9      bad
chromium@515010      22.0154 +- 1.16692       6      bad
chromium@515020      22.467 +- 1.75251        6      bad
chromium@515040      22.5129 +- 1.86614       6      bad
chromium@515080      21.9939 +- 0.973934      6      bad
chromium@515160      22.5447 +- 1.35272       6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=GUIMark.Vector.Chart.Test smoothness.gpu_rasterization.tough_path_rendering_cases

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8962854174952911536


For feedback, file a bug with component Speed>Bisection
►

Sign in to add a comment