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

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


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

chromium-rel-mac11

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

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


===== TESTED REVISIONS =====
Revision                             Mean     Std Dev  N   Good?
chromium@434183                      150.301  11.512   18  good
chromium@434218                      150.413  7.89924  12  good
chromium@434236                      150.574  2.10402  5   good
chromium@434245                      150.087  4.17634  12  good
chromium@434247                      149.458  5.87953  8   good
chromium@434248                      152.735  17.9106  18  good
chromium@434248,catapult@982d024dad  147.87   10.9895  8   good
chromium@434248,catapult@4e71cc3932  153.988  19.5288  27  unknown
chromium@434248,catapult@3276375d25  154.377  17.8439  27  unknown
chromium@434249                      154.116  13.9041  18  bad
chromium@434253                      415.509  2995.82  12  bad

Bisect job ran on: mac_10_11_perf_bisect
Bug ID: 669607

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...oilevent.com page_cycler_v2.tough_layout_cases
Test Metric: timeToFirstContentfulPaint_avg/pcv1-warm/http___oilevent.com
Relative Change: 176.45%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_11_perf_bisect/builds/1074
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8994633236161888560


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

| 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/8994610427322472288

Could this be due to the catapult roll?

Restricted blamelist: https://chromium.googlesource.com/chromium/src/+log/63aab09e70ad0a7594a544a7f1b5f9415efafafb%5E..6e523087878a0b07c4781fa4b793638a3829b075?pretty=fuller

===== 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@434249  153.665  16.8778  27  good
chromium@434253  154.246  15.6849  27  bad

Bisect job ran on: mac_10_11_perf_bisect
Bug ID: 669607

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...oilevent.com page_cycler_v2.tough_layout_cases
Test Metric: timeToFirstContentfulPaint_avg/pcv1-warm/http___oilevent.com
Relative Change: None

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_11_perf_bisect/builds/1079
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8994610427322472288


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

| 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/8994605755791032000

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


===== SUSPECTED CL(s) =====
Subject : Update ts_proxy to latest commit
Author  : nednguyen
Commit description:
  
For all the changes, see: https://github.com/WPO-Foundation/tsproxy/compare/6fae6141104d077c8ceb1136b6ddee5b98f30240...9ae7d2ff822cb7cef15bc54ff614273c99691744

The main change is "Reduced CPU impact when idle or running in bypass mode".

Bug: https://code.google.com/p/chrome-os-partner/issues/detail?id=60009

BUG=chromium:653519

Review-Url: https://codereview.chromium.org/2516973005
Commit  : 4e71cc39324b205febf5a4cfa3a089a1e2aeab74
Date    : Wed Nov 23 17:55:09 2016


===== TESTED REVISIONS =====
Revision                             Mean     Std Dev  N   Good?
chromium@434183                      148.772  8.57599  12  good
chromium@434218                      148.162  6.47222  8   good
chromium@434236                      149.292  5.65046  12  good
chromium@434245                      148.647  8.30405  12  good
chromium@434247                      147.181  4.69663  8   good
chromium@434248                      147.563  2.78001  8   good
chromium@434248,catapult@982d024dad  146.506  6.46461  8   good
chromium@434248,catapult@4e71cc3932  151.714  4.16165  5   bad    <--
chromium@434249                      152.961  2.00335  5   bad
chromium@434253                      153.717  10.6308  8   bad

Bisect job ran on: mac_10_11_perf_bisect
Bug ID: 669607

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...oilevent.com page_cycler_v2.tough_layout_cases
Test Metric: timeToFirstContentfulPaint_avg/pcv1-warm/http___oilevent.com
Relative Change: 3.32%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_11_perf_bisect/builds/1080
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8994605755791032000


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

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

Patrick: is it possible that reducing the CPU impact of ts_proxy cause a small regression? If you believe so, I think we can mark this as expected.

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