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

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


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

chromium-rel-win8-dual

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

=== Auto-CCing suspected CL author v8-autoroll@chromium.org ===

Hi v8-autoroll@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 : Update V8 DEPS.
Author  : v8-autoroll
Commit description:
  
Rolling v8/build to 92c13104dd5f9f25e115e382d5ab8af33a8b883f

Rolling v8/third_party/instrumented_libraries to f15768d7fdf68c0748d20738184120c8ab2e6db7

Rolling v8/tools/mb to ca9b59f105c3457e5ac5ba2f5a04d435436fa5de

TBR=machenbach@chromium.org,vogelheim@chromium.org,hablich@chromium.org

Review-Url: https://codereview.chromium.org/2188413003
Cr-Commit-Position: refs/heads/master@{#38184}
Commit  : c266607eed670e2644cb44e0903fcebe6f2d9036
Date    : Fri Jul 29 19:53:57 2016


===== TESTED REVISIONS =====
Revision                       Mean     Std Dev  N  Good?
chromium@408840                21286.9  272.85   5  good
chromium@408843                21470.6  520.303  8  good
chromium@408843,v8@77c9cb8341  21727.5  229.858  8  good
chromium@408843,v8@c266607eed  22050.5  276.501  8  bad    <--
chromium@408844                22227.0  119.475  5  bad
chromium@408845                22329.2  106.371  5  bad
chromium@408849                22129.2  385.579  5  bad
chromium@408858                22036.7  251.237  5  bad

Bisect job ran on: win_8_perf_bisect
Bug ID: 633117

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests dromaeo.domcorequery
Test Metric: dom/dom
Relative Change: 3.52%
Score: 98.0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_8_perf_bisect/builds/2077
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005542122474691520


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

| 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 got assigned to v8-autoroll - Annie, anything we can do to avoid regressions getting auto-assigned to bots?

Reassigning to machenbach@ in any case, I'm not sure if there was anything in that roll which could have affected performance?

The bisect result is wrong as it points into a deps change inside v8. I don't know what I could do here. Could somebody retrigger the bisects?

I'm WontFix-ing this bug as the regression has recovered.