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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=3283a8237f98a34d9bce9d47d181bb7467d499afc8793a97c610746d9ff1c75c


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

linux-release

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

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

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : smoothness.tough_filters_cases
  Metric       : frame_times/Analog Clock SVG

Revision             Result                    N
chromium@485714      16.68 +- 0.0460196        21      good
chromium@485896      16.6766 +- 0.0436865      21      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 --story-filter=Analog.Clock.SVG smoothness.tough_filters_cases

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8974158287862297088


For feedback, file a bug with component Speed>Bisection

Assigning to senorblanco, owner of smoothness.tough_filters_cases: both ToT and ref build got very noisy on linux, any thoughts on how to address?

No idea off the top of my head. Has the bot been rebooted since it started happening?

Yep, looks like the bot was down from July 3 to July 12, and after restarting this started.

In that case, I've got nothin'. :(

We're probably going to move to new linux hardware anyway.