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

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


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

win-zenbook

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/528
Failure reason: the build has failed due to infrastructure failure.

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

Kicked a bisect with range 421484..421796, as that seems broader than the original bisect, even though the first two attempts failed due to infra failures.

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

Hi robliao@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 fieldtrial_util To Handle Combined Fieldtrial Config Format
Author  : robliao
Commit description:
  
BUG=649363, 650705

Review-Url: https://codereview.chromium.org/2373843002
Cr-Commit-Position: refs/heads/master@{#421670}
Commit  : 8da8200a279fcafc4a7c68f2e6ef95f4d721bb3a
Date    : Wed Sep 28 22:51:09 2016


===== TESTED REVISIONS =====
Revision         Mean    Std Dev  N   Good?
chromium@421484  167478  119839   55  good
chromium@421640  166716  117728   55  good
chromium@421660  167095  113135   55  good
chromium@421665  166401  116361   55  good
chromium@421668  166692  117194   55  good
chromium@421669  166048  113633   55  good
chromium@421670  208656  130015   55  bad    <--
chromium@421679  208287  115622   55  bad
chromium@421718  208676  116258   55  bad
chromium@421796  210235  140007   55  bad

Bisect job ran on: winx64_zen_perf_bisect
Bug ID: 653208

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests storage.indexeddb_endure
Test Metric: vm_working_set_final_size_total/vm_working_set_final_size_total
Relative Change: 25.53%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/611
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8995245557204549616


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

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

Redirecting to jbauman based off of  https://crbug.com/648644 . This bug is potentially a dupe of that one.

https://crrev.com/421670 is a tooling fix that reenables the accidentally disabled experiments on the waterfall due to https://crrev.com/420118.

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

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

Hi robliao@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 : robliao
  Commit : 8da8200a279fcafc4a7c68f2e6ef95f4d721bb3a
  Date   : Wed Sep 28 22:51:09 2016
  Subject: Update fieldtrial_util To Handle Combined Fieldtrial Config Format

Bisect Details
  Configuration: winx64_zen_perf_bisect
  Benchmark    : storage.indexeddb_endure
  Metric       : vm_working_set_final_size_total/vm_working_set_final_size_total
  Change       : 24.02% | 167318.727273 -> 207510.969697

Revision             Result                 N
chromium@421604      167319 +- 3768.11      6      good
chromium@421650      166711 +- 1375.16      6      good
chromium@421662      167005 +- 3703.59      6      good
chromium@421668      168430 +- 2024.38      6      good
chromium@421669      167820 +- 1325.75      6      good
chromium@421670      208443 +- 3114.94      6      bad       <--
chromium@421671      208505 +- 1641.7       6      bad
chromium@421673      207338 +- 6560.85      6      bad
chromium@421695      207511 +- 2999.49      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests storage.indexeddb_endure

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

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


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