Fixing component

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

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

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : v8.runtime_stats.top_25
  Metric       : API:duration_avg/http___meta.discourse.org

Revision             Result                  N
chromium@487550      9.479 +- 49.5735        21      good
chromium@487730      22.7316 +- 300.259      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...meta.discourse.org v8.runtime_stats.top_25

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

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


For feedback, file a bug with component Speed>Bisection

Chromeperf link for this bug: https://chromeperf.appspot.com/group_report?bug_id=747799

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

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

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

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : v8.runtime_stats.top_25
  Metric       : API:duration_avg/https___cdn.ampproject.org_c_www.bbc.co.uk_news_amp_37344292_log_3

Revision             Result                  N
chromium@487550      6.90224 +- 36.0177      21      good
chromium@487730      6.89014 +- 36.3972      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=https...cdn.ampproject.org.c.www.bbc.co.uk.news.amp.37344292.log.3 v8.runtime_stats.top_25

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

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


For feedback, file a bug with component Speed>Bisection

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

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

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : v8.runtime_stats.top_25
  Metric       : API:duration_avg/http___www.amazon.com_s_?field-keywords_v8

Revision             Result                  N
chromium@487550      3.34371 +- 3.25206      21      good
chromium@487730      3.18462 +- 2.49071      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.amazon.com.s..field.keywords.v8 v8.runtime_stats.top_25

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

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


For feedback, file a bug with component Speed>Bisection

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

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : v8.runtime_stats.top_25
  Metric       : Parse:duration_avg/http___www.amazon.com_s_?field-keywords_v8

Revision             Result                    N
chromium@487450      0.551048 +- 0.364059      21      good
chromium@487830      0.553286 +- 0.498825      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.amazon.com.s..field.keywords.v8 v8.runtime_stats.top_25

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

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


For feedback, file a bug with component Speed>Bisection

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

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

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : v8.runtime_stats.top_25
  Metric       : API:duration_avg/http___meta.discourse.org

Revision             Result                  N
chromium@487550      5.14567 +- 1.86534      21      good
chromium@487730      5.33381 +- 1.71119      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...meta.discourse.org v8.runtime_stats.top_25

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

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


For feedback, file a bug with component Speed>Bisection

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

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

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

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : v8.runtime_stats.top_25
  Metric       : API:duration_avg/http___maps.google.co.jp_maps_search_restaurant+tokyo

Revision             Result                  N
chromium@487213      7.14957 +- 8.82079      21      good
chromium@488385      7.60671 +- 11.3675      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...maps.google.co.jp.maps.search.restaurant.tokyo v8.runtime_stats.top_25

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

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


For feedback, file a bug with component Speed>Bisection

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

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : v8.runtime_stats.top_25
  Metric       : API:duration_avg/http___hi.wikipedia.org_wiki_%E0%A4%AE%E0%A5%81%E0%A4%96%E0%A4%AA%E0%A5%83%E0%A4%B7%E0%A5%8D%E0%A4%A0

Revision             Result                  N
chromium@487213      5.01029 +- 1.54725      21      good
chromium@488385      7.61181 +- 51.2736      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...hi.wikipedia.org.wiki..E0.A4.AE.E0.A5.81.E0.A4.96.E0.A4.AA.E0.A5.83.E0.A4.B7.E0.A5.8D.E0.A4.A0 v8.runtime_stats.top_25

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

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


For feedback, file a bug with component Speed>Bisection

Bots can't repro it. I am tempted to close this issue as not actionable. WDYT?

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot