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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggsqOqwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg_P7brAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggrqg4woM


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

chromium-rel-mac-retina
chromium-rel-mac11
chromium-rel-mac11-pro

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

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

Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : page_cycler_v2.typical_25
  Metric       : timeToFirstMeaningfulPaint_avg/pcv1-warm/http___www.flickr.com_search_?q_monkeys_f_hp

Revision             Result                  N
chromium@463519      265.251 +- 520.141      21      good
chromium@463591      702.656 +- 1496.95      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=http...www.flickr.com.search..q.monkeys.f.hp page_cycler_v2.typical_25

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8982422283615750128

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5669535346065408


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

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

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

Suspected Commit
  Author : delphick
  Commit : d8ade60fbe0ea954ecd5f186c36e6d0ac045c28c
  Date   : Tue Apr 11 09:56:28 2017
  Subject: No longer clamp setTimeout(..., 0) to 1ms.

Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : page_cycler_v2.typical_25
  Metric       : timeToFirstMeaningfulPaint_avg/pcv1-warm/http___www.flickr.com_search_?q_monkeys_f_hp
  Change       : 177.08% | 292.084428574 -> 809.310857145

Revision             Result                  N
chromium@463519      292.084 +- 512.461      14      good
chromium@463555      338.718 +- 453.062      9       good
chromium@463573      278.783 +- 372.888      9       good
chromium@463582      208.883 +- 41.74        9       good
chromium@463587      198.539 +- 29.3385      6       good
chromium@463589      275.884 +- 366.219      9       good
chromium@463590      305.76 +- 412.036       9       good
chromium@463591      809.311 +- 960.727      14      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=http...www.flickr.com.search..q.monkeys.f.hp page_cycler_v2.typical_25

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8982416691794194688

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5669535346065408


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!