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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgzNXR-woM


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

chromium-rel-mac11

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

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

Hi jarin@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 : jarin
  Commit : 154369bb5af9b2e1ff6094df52b94f56219a402c
  Date   : Tue Mar 21 16:59:41 2017
  Subject: Reset the runtime profiler ticks for bytecode if IC state changes.

Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop_classic
  Metric       : JavaScript:duration_avg/browse_media/browse_media_imgur
  Change       : 6.20% | 4356.286 -> 4626.24133333

Revision                           Result                  N
chromium@458507                    4356.29 +- 109.29       6      good
chromium@458564                    4435.93 +- 83.6638      6      good
chromium@458592                    4449.93 +- 173.583      9      good
chromium@458596                    4437.48 +- 91.166       9      good
chromium@458597                    4428.81 +- 84.153       6      good
chromium@458597,v8@5097f3d37c      4405.44 +- 87.5236      6      good
chromium@458597,v8@154369bb5a      4600.82 +- 102.931      6      bad       <--
chromium@458597,v8@9dfa46395a      4631.96 +- 108.306      6      bad
chromium@458598                    4618.2 +- 67.4212       6      bad
chromium@458599                    4577.3 +- 282.382       9      bad
chromium@458606                    4592.15 +- 77.2719      6      bad
chromium@458620                    4626.24 +- 91.5144      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=browse.media.imgur v8.runtimestats.browsing_desktop_classic

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

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


| 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!

Runtime profiler has been redesigned since then.