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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgzK3i6gkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgzKPwtgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgzLKmrQoM


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

chromium-rel-win7-gpu-ati

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

=== Auto-CCing suspected CL author ericrk@chromium.org ===

Hi ericrk@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : ericrk
  Commit : 45b88dc78af5c27d0cd462889fe44b62e313a189
  Date   : Mon Mar 20 21:38:21 2017
  Subject: Enable GPU Raster on all GCN1+ Cards

Bisect Details
  Configuration: winx64ati_perf_bisect
  Benchmark    : smoothness.top_25_smooth
  Metric       : mean_input_event_latency/https___www.google.com_calendar_
  Change       : 185.46% | 8.74266666667 -> 24.9565

Revision             Result                  N
chromium@458172      8.74267 +- 5.78451      6      good
chromium@458189      7.7295 +- 3.68964       6      good
chromium@458193      8.16683 +- 4.89259      6      good
chromium@458195      7.9705 +- 5.08125       6      good
chromium@458196      8.5515 +- 5.38584       6      good
chromium@458197      24.5465 +- 10.0428      6      bad       <--
chromium@458205      26.0767 +- 10.3424      6      bad
chromium@458237      23.1313 +- 7.03698      6      bad
chromium@458302      24.9565 +- 11.905       6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=https...www.google.com.calendar. smoothness.top_25_smooth

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

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


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

Explictly assigning. A CL you landed tripped one of the speed metrics we measure in the lab. If this is the first time this has happened to one of your CLs, or if it's been a while, please read: https://chromium.googlesource.com/chromium/src/+/master/docs/speed/addressing_performance_regressions.md

We're looking for one of the following:
1. Justification via explanation
2. Plan to revert or fix
3. Angry rage throwing of equipment at my head

Just be aware that I'm trained in trumpet playing and First Aid and am not afraid to use it.

Note: This was a bulk edit message and not very personal.

The numbers dropped back down.