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

Issue 741705 link

Starred by 2 users
Status: Duplicate
Merged: issue 741725
Owner: ----
Closed: Jul 2017
Cc:
█ pmeenan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

7.7%-80.1% regression in smoothness.tough_canvas_cases at 485301:485472

Project Member Reported by pmeenan@chromium.org, Jul 12 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jul 12 2017 

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

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


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

chromium-rel-win10
chromium-rel-win7-dual
chromium-rel-win7-gpu-intel
chromium-rel-win8-dual
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jul 12 2017 


=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : smoothness.gpu_rasterization.tough_path_rendering_cases
  Metric       : frame_times/MotionMark Canvas Fill Shapes


To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=MotionMark.Canvas.Fill.Shapes 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/8974257339084832880


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

Comment 5 by 42576172...@developer.gserviceaccount.com, Jul 22 2017

Mergedinto: 741725
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Justin Novosad
  Commit : 3750a7881ce851e03ce6177dca30307eb4a7f5c6
  Date   : Mon Jul 10 20:50:59 2017
  Subject: Disabling display list 2D canvas by default

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : smoothness.tough_canvas_cases
  Metric       : frame_times/frame_times
  Change       : 19.75% | 31.7569565131 -> 38.0275450721

Revision             Result                   N
chromium@485312      31.757 +- 0.350641       6      good
chromium@485343      31.5207 +- 0.259606      6      good
chromium@485358      31.5265 +- 0.26248       6      good
chromium@485366      31.5898 +- 0.246746      6      good
chromium@485370      31.6668 +- 0.211451      6      good
chromium@485371      38.0269 +- 0.681799      6      bad       <--
chromium@485372      38.0285 +- 0.36169       6      bad
chromium@485373      38.0735 +- 0.793409      6      bad
chromium@485433      38.0275 +- 0.640703      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests smoothness.tough_canvas_cases

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

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


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

Sign in to add a comment