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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgy4vBrwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgy5e4qgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgq7iLsgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgy-CvuwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgq9rFuQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgq_zOrAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgy4iR8wkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgy-3NqgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgy62FuQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgy_XHsAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgq_yZvQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgi4PY4AoM


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

linux-release

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

===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: 
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N   Good?
chromium@432340  6844791  14491923  45  good
chromium@432373  6960193  14277672  45  unknown
chromium@432405  7924330  13846755  45  bad

Bisect job ran on: linux_perf_bisect
Bug ID: 666395

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests tracing.tracing_with_debug_overhead
Test Metric: Max event size in bytes per second_avg/Max event size in bytes per second_avg
Relative Change: 15.77%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/linux_perf_bisect/builds/6847
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8995722475543570896


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

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

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

===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N   Good?
chromium@432300  7606749  19585772  45  good
chromium@432475  8319442  20299358  45  bad

Bisect job ran on: winx64ati_perf_bisect
Bug ID: 666395

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests tracing.tracing_with_debug_overhead
Test Metric: Max event size in bytes per second_sum/Max event size in bytes per second_sum
Relative Change: None

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64ati_perf_bisect/builds/1648
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8995271424924781584


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

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

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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

The bisect was able to narrow the range, you can try running with:
  good_revision: 41e94820ce6ca738bdb2d319740ae79d875380e2
  bad_revision : 035067294b27c4fc3ef2e10db62037c8f3f50359


If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : tracing.tracing_with_debug_overhead
  Metric       : Max event size in bytes per second_min/Max event size in bytes per second_min
  Change       : 14.63% | 6854512.42593 -> 7857003.51852

Revision             Result                 N
chromium@432340      6854512 +- 292713      6      good
chromium@432373      6924520 +- 237893      6      good
chromium@432389      6916690 +- 356549      6      good
chromium@432391      7653830 +- 291093      6      bad
chromium@432393      7724798 +- 211140      6      bad
chromium@432397      7638564 +- 278749      6      bad
chromium@432405      7857004 +- 370332      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 tracing.tracing_with_debug_overhead

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

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


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

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

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

About half of the regressions recovered.  The rest are too noisy to have successful bisects.