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

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


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

chromium-rel-mac12

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

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

Suspected Commit
  Author : perezju
  Commit : 122dd5e91bf64888049459ce73a8fd34c084cfe0
  Date   : Mon Aug 14 12:28:51 2017
  Subject: [Telemetry] Reuse shared state between story runs

Bisect Details
  Configuration: mac_10_12_perf_bisect
  Benchmark    : blink_perf.shadow_dom
  Metric       : style-sheet-insert/style-sheet-insert
  Change       : 4.44% | 11.0184444444 -> 11.462

Revision                                 Result                   N
chromium@494020                          11.0184 +- 0.599089      9       good
chromium@494034                          11.0202 +- 0.316112      6       good
chromium@494041                          10.9601 +- 0.448527      9       good
chromium@494044                          11.1655 +- 1.39141       14      good
chromium@494046                          11.0964 +- 1.40368       9       good
chromium@494046,catapult@122dd5e91b      11.6041 +- 2.82116       14      bad       <--
chromium@494047                          11.462 +- 0.583553       9       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 blink_perf.shadow_dom

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

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


For feedback, file a bug with component Speed>Bisection