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

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


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

android-nexus6

Assigning to chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com because this is the only CL in range:
Roll src/third_party/chromite/ e6139afa1..44123785c (2 commits)

https://chromium.googlesource.com/chromiumos/chromite.git/+log/e6139afa10f8..44123785ca9a

$ git log e6139afa1..44123785c --date=short --no-merges --format='%ad %ae %s'
2018-03-24 ihf chromeos-config: mark eve-arcnext-chrome-pfq important.
2018-03-23 achuith cros_vm: Determine SDK version outside SDK shell.

Created with:
  roll-dep src/third_party/chromite
BUG=chromium:825539, chromium:823996 


The AutoRoll server is located here: https://chromite-chromium-roll.skia.org

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=chrome-os-gardeners@chromium.org

Change-Id: Icb8dcad2d3ee70b331e2446f9f873e2c21c385d8
Reviewed-on: https://chromium-review.googlesource.com/979598
Reviewed-by: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#545707}

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14e6bde8c40000

This graph is pretty noisy, bisecting on a wider range.

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/14e6bde8c40000

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/149d30d3c40000

📍 Found significant differences after each of 3 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/149d30d3c40000

Force proper code aligment in wasm serializer. by ivo.markovic@mips.com
https://chromium.googlesource.com/v8/v8/+/5dca2bd7ee5e854090e37633684a81eceb60f9ee

Update V8 to version 6.7.159.1 (cherry-pick). by v8-autoroll@chromium.org
https://chromium.googlesource.com/chromium/src/+/6dda25c3a237e3ea2dec20a830c58973918ea9fd

[ic] Use Map as transition handlers instead of StoreHandler objects. by ishell@chromium.org
https://chromium.googlesource.com/v8/v8/+/78c6bbd930b9138002cfb52642b90b9aab104a78

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Looking at the bisect results the culprit is indeed more likely:

[ic] Use Map as transition handlers instead of StoreHandler objects. by ishell@chromium.org
https://chromium.googlesource.com/v8/v8/+/78c6bbd930b9138002cfb52642b90b9aab104a78

ishell, can you investigate?

perf sheriff triage:

since ishell@'s last login was > 30 days ago, let me assign verwaest@ who reviewed the suspected CL instead.