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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg-5He5goM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg56PAowkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg58nOvAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg59zMtAkM


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

chromium-rel-mac10

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

===== 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@436184  6312112  27623975  45  good
chromium@436189  6370324  27363008  45  bad

Bisect job ran on: mac_10_10_perf_bisect
Bug ID: 671230

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: Total trace size in bytes_max/Total trace size in bytes_max
Relative Change: 0.92%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_10_perf_bisect/builds/2499
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8994097731219046928


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

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

Notes:
 - All of these alerts are on the same bot (chromium-rel-mac10).
 - This increase appears after another increase (bug 671057).

Looking at the individual page results, there's no clear increase on any one page. This may just be noise.

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

===== 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@436184  6159196  26783298  45  good
chromium@436189  6152016  23673888  36  bad

Bisect job ran on: mac_10_10_perf_bisect
Bug ID: 671230

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: Total trace size in bytes_min/Total trace size in bytes_min
Relative Change: 0.12%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_10_perf_bisect/builds/2501
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993986885588948304


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

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

Closing.  Levels have returned to where they were before this bug (though not the earlier, massive regression)

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

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

Bisect Details
  Configuration: mac_10_10_perf_bisect
  Benchmark    : tracing.tracing_with_debug_overhead
  Metric       : Total trace size in bytes_max/Total trace size in bytes_max

Revision             Result                   N
chromium@436184      6312112 +- 27623975      45      good
chromium@436189      6370324 +- 27363008      45      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/8982620213174337104

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


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