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

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


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

android-nexus7v2

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

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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@412301  13836.9  265.125  8  good
chromium@412306  13788.4  114.071  5  good
chromium@412307  21008.4  552.585  5  bad
chromium@412308  20685.4  936.49   5  bad
chromium@412309  21044.2  553.932  5  bad
chromium@412311  20693.4  434.141  5  bad
chromium@412320  21430.0  1392.06  5  bad
chromium@412338  19217.0  3464.71  8  bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 639773

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests tracing.tracing_with_debug_overhead
Test Metric: Max number of events per second/Max number of events per second
Relative Change: 27.14%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3235
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9003641162464416688


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

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

Marking as fixed :- should have marked as ignore rather opening a bug. The regression appears to be a revert to old performance figures after temporary boost.