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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgyrDCuQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgivj8gggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgipr_6wkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgirGg7wkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg8pyanAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgiqnOhgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg8uHtkgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg8q_PmQgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgisTI-QsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg8vbagggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgipm9qgsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgivCAsQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgst-19gsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgirCmtgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgiuDqswsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgit7K9QsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgiqKe9AgM


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

chromium-rel-win10
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-x64-dual
chromium-rel-win8-dual

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

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


===== SUSPECTED CL(s) =====
Subject : Disable Full-WPO for the x64 official build (non-PGO).
Author  : sebmarchand
Commit description:
  
Disable Full-WPO for the x64 official builds (this doesn't
affect the PGO builds).

This should help me to get an official
"non-PGO & non-WPO" build that I can compare against an official PGO
build.

Also I'm not sure if it's worth keeping WPO turned on for the official
builds at the moment ? We don't ship these builds (we ship the PGO ones)
and so this only slowdown the builders that build an official x64 build
for testing purposes (especially considering that they need to link all the unittests with Full-WPO)

BUG= 490934 , 617982

Review-Url: https://codereview.chromium.org/2142603002
Cr-Commit-Position: refs/heads/master@{#405164}
Commit  : 0d74d7f71c93bfc3b32653de7958ff84d173937d
Date    : Wed Jul 13 15:42:28 2016


===== TESTED REVISIONS =====
Revision         Mean    Std Dev   N  Good?
chromium@405150  36.14   1.16413   5  good
chromium@405161  35.392  0.666648  5  good
chromium@405163  35.823  0.876603  5  good
chromium@405164  41.926  1.33118   5  bad    <--
chromium@405166  43.406  5.07799   5  bad
chromium@405171  39.536  1.58661   5  bad
chromium@405202  40.854  1.07339   5  bad

Bisect job ran on: win_x64_perf_bisect
Bug ID: 628452

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests service_worker.service_worker_micro_benchmark
Test Metric: concurrent_100_response_90_percentile/concurrent_100_response_90_percentile
Relative Change: 13.04%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_x64_perf_bisect/builds/1325
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9007113492459495216


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

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