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

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


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

chromium-rel-win8-dual

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

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

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : total:500ms_window:renderer_eqt_max/load_accessibility_shopping/load_accessibility_shopping_amazon

Revision             Result                  N
chromium@514983      229.295 +- 1210.21      21      good
chromium@515078      280.532 +- 1804.82      21      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=load.accessibility.shopping.amazon system_health.common_desktop

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

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


For feedback, file a bug with component Speed>Bisection

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

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

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


Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : total:500ms_window:renderer_eqt_max/browse_tech/browse_tech_discourse_infinite_scroll


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=browse.tech.discourse.infinite.scroll system_health.common_desktop

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

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


For feedback, file a bug with component Speed>Bisection

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

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

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : total:500ms_window:renderer_eqt_max/load_accessibility_shopping/load_accessibility_shopping_amazon

Revision             Result                  N
chromium@515000      241.505 +- 1651.62      21      good
chromium@515233      222.735 +- 1620.96      21      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=load.accessibility.shopping.amazon system_health.common_desktop

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

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


For feedback, file a bug with component Speed>Bisection

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

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

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : total:500ms_window:renderer_eqt_max/load_accessibility_shopping/load_accessibility_shopping_amazon

Revision             Result                  N
chromium@514000      298.333 +- 1818.08      21      good
chromium@515100      236.391 +- 1646.55      21      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=load.accessibility.shopping.amazon system_health.common_desktop

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

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


For feedback, file a bug with component Speed>Bisection

Trying on a few different hardware configs since these all ran on win8 and now we can see pinpoint results.

Tim, how confident are we in the eqt metrics? (And at what start point, I'm triaging in november right now)

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14e6fd9f040000

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14d7b9df040000

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/14d7b9df040000

The traces for those points show a real regression.

There's a ScheduledActionBeginLayerTreeFrameSinkCreation task that took 1.8 seconds in the second trace.

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/14e6fd9f040000

tdresser, any ideas what the next step in triage should be?

We've been unable to repro enough that I suspect the change I saw was just noise. Marking WontFix.