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

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


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

chromium-rel-win10

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

=== 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: winx64_10_perf_bisect
  Benchmark    : loading.desktop
  Metric       : timeToFirstMeaningfulPaint_avg/pcv1-warm/FC2Blog
  Change       : 2592.00% | 85.1635 -> 2292.603

Revision                                 Result                  N
chromium@494039                          85.1635 +- 37.8013      6      good
chromium@494044                          85.492 +- 14.356        6      good
chromium@494046                          80.6967 +- 22.026       6      good
chromium@494046,catapult@122dd5e91b      2278.53 +- 508.081      6      bad       <--
chromium@494047                          2246.91 +- 325.966      6      bad
chromium@494049                          2346.16 +- 847.774      6      bad
chromium@494059                          2240.35 +- 393.626      6      bad
chromium@494079                          2283.15 +- 440.598      6      bad
chromium@494119                          2292.6 +- 249.11        6      bad

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=FC2Blog loading.desktop

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

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


For feedback, file a bug with component Speed>Bisection