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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgiN3OpwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgiOvTqwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgiNTHvQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgiObqogkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg8P-5tAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg8PuSqgoM


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

chromium-rel-mac-retina
chromium-rel-mac10

Kicked off a bisect on bing.com page in https://chromeperf.appspot.com/buildbucket_job_status/9016662095336369824

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

Hi aiolos@chromium.org, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : Fix flash local path.
Author  : aiolos
Commit description:
  
BUG= 568599 

Review URL: https://codereview.chromium.org/1845653002

Cr-Commit-Position: refs/heads/master@{#384072}
Commit  : 4187881d1cf074854b65d1d86492a09a838b0f8c
Date    : Wed Mar 30 20:15:52 2016


===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@384030         6885.6      339.907782  5           good
chromium@384054         6916.8      257.820092  5           good
chromium@384067         6821.2      218.266351  5           good
chromium@384070         6889.2      198.204944  5           good
chromium@384071         6798.8      292.903909  5           good
chromium@384072         29021.4     1350.885191 5           bad         <-
chromium@384073         27454.8     1171.657672 5           bad
chromium@384079         28868.2     1385.513876 5           bad

Bisect job ran on: mac_retina_perf_bisect
Bug ID: 599486

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --also-run-disabled-tests tracing.tracing_with_debug_overhead
Test Metric: Max number of events per second/http___www.bing.com_
Relative Change: 319.25%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1233
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9016662095336369824


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=599486

| 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 Tests>AutoBisect.  Thank you!

Hmhh, I thinks this is expected because before Kari's patch, the browser was started without flash enabled.

Yes, it is expected.