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

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


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

android-nexus5X

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

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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N  Good?
chromium@413385  10.5368  0.39485   5  good
chromium@413390  10.5858  0.386372  5  good
chromium@413391  13.9244  1.2778    5  bad
chromium@413392  13.3714  0.78006   5  bad
chromium@413394  13.5664  0.546652  5  bad
chromium@413402  13.4036  0.397326  5  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 641015

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.top_25_smooth
Test Metric: mean_input_event_latency/Pinterest
Relative Change: 27.21%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/604
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9003339370253133808


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

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

Looks like r413391 is a catapult roll, and bisect is not diving into catapult. 
There is only 1 CL crrev.com/947506bacfb5047857a52033256635faebf38af2 in this roll.
nednguyen@, Do you think your CL might have caused this regression?

Blocking on  bug 641133 , about failing to descend into rolls.

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

Started new bisect: https://chromeperf.appspot.com/buildbucket_job_status/9002975810363602400

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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N  Good?
chromium@413382  28.7785  0.367983  5  good
chromium@413390  29.8337  0.902536  5  good
chromium@413391  48.3493  4.94529   5  bad
chromium@413392  53.2121  6.31251   5  bad
chromium@413394  52.7105  10.0575   5  bad
chromium@413398  46.0568  3.35518   5  bad

Bisect job ran on: winx64_10_perf_bisect
Bug ID: 641015

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.top_25_smooth
Test Metric: frame_times/ESPN
Relative Change: 60.04%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_10_perf_bisect/builds/697
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9002975810363602400


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

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

=== Auto-CCing suspected CL author catapult-deps-roller@chromium.org ===

Hi catapult-deps-roller@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 : Roll src/third_party/catapult/ cda4e72f8..947506bac (1 commit).
Author  : catapult-deps-roller
Commit description:
  
https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/cda4e72f8776..947506bacfb5

$ git log cda4e72f8..947506bac --date=short --no-merges --format='%ad %ae %s'

BUG=639632

TBR=catapult-sheriff@chromium.org

Review-Url: https://codereview.chromium.org/2264903002
Cr-Commit-Position: refs/heads/master@{#413391}
Commit  : 8c8697b3bef3a2d9f0cf1ab895905bdf3b4b66c4
Date    : Mon Aug 22 02:52:20 2016


===== TESTED REVISIONS =====
Revision                             Mean     Std Dev   N  Good?
chromium@413382                      28.8238  1.61988   5  good
chromium@413390                      29.3411  0.665597  5  good
chromium@413390,catapult@947506bacf  29.9984  1.38262   5  good
chromium@413391                      53.4086  14.8411   5  bad    <--
chromium@413392                      50.6068  5.45942   5  bad
chromium@413394                      57.182   8.91492   5  bad
chromium@413398                      51.1888  6.01803   5  bad

Bisect job ran on: winx64_10_perf_bisect
Bug ID: 641015

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.top_25_smooth
Test Metric: frame_times/ESPN
Relative Change: 77.59%
Score: 95.0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_10_perf_bisect/builds/698
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9002958799056492480


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

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

Ned, bisect continues to point to https://codereview.chromium.org/2267613002 ('Revert "[telemetry] Wire TsProxy through telemetry's network stack."')

Does that make sense?

I didn't expected that enabling ts_proxy will improve the smoothness.top_25_smooth metrics at all (hence revert regressing it)!

Though should we just mark this as won't fix because this is regression due to test change and not binary change? 

Won't fix since tsproxy is relanded.