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

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


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

android-nexus5

Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Trying another bisect.

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

Hi mdjones@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 : Implement OverlayPanels as SceneOverlays
Author  : mdjones
Commit description:
  
Use the SceneOverlay infrastructure to draw on top of Chrome send events
to OverlayPanels rather than using layout switching.

BUG=584340

Review-Url: https://codereview.chromium.org/1716653002
Cr-Commit-Position: refs/heads/master@{#393851}
Commit  : 5a5b9fbe34f23087353c763ec5420deb075194d9
Date    : Mon May 16 17:06:45 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev    N  Good?
chromium@393844  5.07755  0.0251547  5  good
chromium@393850  5.06829  0.0678436  5  good
chromium@393851  5.37329  0.0613924  5  bad    <--
chromium@393852  5.3812   0.0972481  5  bad
chromium@393853  5.40527  0.0611305  5  bad
chromium@393855  5.4144   0.12359    5  bad
chromium@393865  5.39882  0.0274045  5  bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 613184

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests thread_times.tough_scrolling_cases
Test Metric: thread_raster_cpu_time_per_frame/thread_raster_cpu_time_per_frame
Relative Change: 6.33%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/3792
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9008307661884287488


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

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

This issue has been moved once and is lower than Pri-1. Removing the milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

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

mdjones: it looks like your CL caused a regression. Can you investigate?

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


===== SUSPECTED CL(s) =====
Subject : Implement OverlayPanels as SceneOverlays
Author  : mdjones
Commit description:
  
Use the SceneOverlay infrastructure to draw on top of Chrome send events
to OverlayPanels rather than using layout switching.

BUG=584340

Review-Url: https://codereview.chromium.org/1716653002
Cr-Commit-Position: refs/heads/master@{#393851}
Commit  : 5a5b9fbe34f23087353c763ec5420deb075194d9
Date    : Mon May 16 17:06:45 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N  Good?
chromium@393840  37.2953  0.381036  5  good
chromium@393846  37.4778  0.359864  5  good
chromium@393849  37.3566  0.488042  5  good
chromium@393850  37.3109  0.119089  5  good
chromium@393851  40.8248  0.484688  5  bad    <--
chromium@393862  41.1168  0.365593  5  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 613184

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests thread_times.tough_scrolling_cases
Test Metric: thread_total_all_cpu_time_per_frame/thread_total_all_cpu_time_per_frame
Relative Change: 10.25%
Score: 99.9

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


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

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

This is a huge CL that changed the way a number of features work in clank; it will take some time to investigate but I'm looking into it.

Friendly perf-sheriff ping, any update on this?

mdjones: another ping about whether there are any updates here?

Not recently. I'll dig into this when I get some time.

Perf sheriff ping: reminder to follow up on possible performance issues

mdjones, have you had any chance to dig into this CL?

+cc tdresser, it looks like this test has stopped reporting data. Has this been moved/renamed/replaced?

Not yet, I've had a few other regressions that needed fixing This is on my list though.

Ping. Any updates? This has been kicked forward in time quite a bit at this point even though this is a known regression. Are there others on your team who might have some cycles to help out?

Looks like the window to fix this has passed. Graphs did eventually come back down