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

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


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

chromium-rel-mac12

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

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

Bisect Details
  Configuration: mac_10_12_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : v8-gc-latency-mark-compactor_max/browse_media/browse_media_imgur

Revision             Result                  N
chromium@490784      17.849 +- 37.6476       21      good
chromium@490826      17.5104 +- 41.3262      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=browse.media.imgur v8.runtimestats.browsing_desktop

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

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


For feedback, file a bug with component Speed>Bisection

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

=== Auto-CCing suspected CL author xunjieli@chromium.org ===

Hi xunjieli@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : Helen Li
  Commit : 05ee1dbfaf0aa7c03b9ea2040f0345277042d0f1
  Date   : Mon Jul 31 13:24:01 2017
  Subject: [wpr-go] Switch system_health_desktop.json to use go

Bisect Details
  Configuration: winx64ati_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : v8-gc-latency-mark-compactor_sum/browse_news/browse_news_flipboard
  Change       : 83.44% | 8.304 -> 15.2325

Revision             Result                   N
chromium@490700      8.304 +- 1.06027         6      good
chromium@490747      9.57767 +- 2.59607       6      good
chromium@490750      8.69667 +- 0.421765      6      good
chromium@490751      13.6182 +- 2.69157       6      bad       <--
chromium@490752      13.1757 +- 1.43258       6      bad
chromium@490753      12.5242 +- 3.09742       6      bad
chromium@490759      13.0512 +- 3.19057       6      bad
chromium@490770      13.1687 +- 6.15474       9      bad
chromium@490793      15.2325 +- 5.37565       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=browse.news.flipboard v8.runtimestats.browsing_desktop

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

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


For feedback, file a bug with component Speed>Bisection

The metric seems to be going down. I will keep an eye on this one.

The metric is relatively consistent after wprgo migration. I will mark this one as WontFix because slight changes in performance characteristics after migration are expected. I didn't see anything obviously wrong going on here.