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

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


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

chromium-rel-win7-dual

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8963323230219072896

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

Hi junov@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== 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: win_perf_bisect
  Benchmark    : smoothness.tough_path_rendering_cases
  Metric       : frame_times/GUIMark Vector Chart Test
  Change       : 20.97% | 32.7532294311 -> 25.8863488201

Revision             Result                   N
chromium@514931      32.7532 +- 1.33002       6      good
chromium@514979      32.7092 +- 1.64613       6      good
chromium@514991      32.6375 +- 1.70523       6      good
chromium@514997      32.9081 +- 0.221622      6      good
chromium@515000      32.3955 +- 1.8339        6      good
chromium@515001      25.7399 +- 4.59732       6      bad       <--
chromium@515002      25.4006 +- 0.687546      6      bad
chromium@515003      24.8707 +- 0.280813      6      bad
chromium@515026      25.8863 +- 5.40613       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 --story-filter=GUIMark.Vector.Chart.Test smoothness.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/8963323230219072896


For feedback, file a bug with component Speed>Bisection

 Issue 783767  has been merged into this issue.

 Issue 783633  has been merged into this issue.

 Issue 783635  has been merged into this issue.

 Issue 783619  has been merged into this issue.

 Issue 783634  has been merged into this issue.

 Issue 783639  has been merged into this issue.

 Issue 783642  has been merged into this issue.

 Issue 783645  has been merged into this issue.

 Issue 783629  has been merged into this issue.

 Issue 783649  has been merged into this issue.

 Issue 783629  has been merged into this issue.

 Issue 784419  has been merged into this issue.

 Issue 784419  has been merged into this issue.

 Issue 784425  has been merged into this issue.

 Issue 784417  has been merged into this issue.

Issue 784366 has been merged into this issue.

Issue 784360 has been merged into this issue.

 Issue 784854  has been merged into this issue.

junov: any update on this bug? It looks like a pretty widespread regression.

This has recovered, but it's not clear to me if it was independent optimizations, or if we fixed this regression.

Justin - any idea?