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

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


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

linux-release

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

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

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : page_cycler_v2.basic_oopif
  Metric       : timeToFirstContentfulPaint_avg/pcv1-cold/http___www.fifa.com_

Revision             Result                  N
chromium@486135      157.019 +- 159.377      21      good
chromium@486218      150.997 +- 15.3571      20      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.fifa.com. page_cycler_v2.basic_oopif

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

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


For feedback, file a bug with component Speed>Bisection

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

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

Suspected Commit
  Author : Camillo Bruni
  Commit : 36421dc467bffcdcb71967ed39dddca1e33d48c6
  Date   : Wed Jul 12 19:11:04 2017
  Subject: [literals] Disable double lazy boilerplate for literals containing Arrays

Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : loading.desktop
  Metric       : cpuTimeToFirstMeaningfulPaint_avg/pcv1-warm/Kakaku
  Change       : 6.68% | 254.470333333 -> 271.477

Revision                           Result                  N
chromium@486193                    254.47 +- 2.89262       6      good
chromium@486248                    256.954 +- 5.85131      6      good
chromium@486248,v8@42c8df3f46      259.398 +- 6.13191      6      good
chromium@486248,v8@34874b3b19      262.926 +- 8.95635      6      good
chromium@486248,v8@36421dc467      277.862 +- 13.2943      5      bad       <--
chromium@486248,v8@fa4ec9fdbe      276.463 +- 18.8964      6      bad
chromium@486249                    273.588 +- 4.33911      6      bad
chromium@486250                    272.379 +- 10.1466      6      bad
chromium@486252                    269.008 +- 7.83652      6      bad
chromium@486255                    273.455 +- 5.94835      6      bad
chromium@486262                    270.372 +- 4.66707      6      bad
chromium@486275                    272.54 +- 4.906         6      bad
chromium@486302                    271.477 +- 9.49132      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=Kakaku loading.desktop

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

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


For feedback, file a bug with component Speed>Bisection