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

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


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

chromium-rel-win7-dual

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


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean    Std Dev  N   Good?
chromium@399388  205504  82912.2  18  good
chromium@399390  196100  73522.5  18  bad

Bisect job ran on: win_perf_bisect
Bug ID: 619496

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests webrtc.datachannel
Test Metric: vm_working_set_final_size_total/vm_working_set_final_size_total
Relative Change: 32.83%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect/builds/6587
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9009983221508006880


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

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

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


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean    Std Dev  N   Good?
chromium@399388  186610  74870.2  18  good
chromium@399390  232356  74738.7  18  bad

Bisect job ran on: win_perf_bisect
Bug ID: 619496

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests webrtc.datachannel
Test Metric: vm_working_set_final_size_total/vm_working_set_final_size_total
Relative Change: 13.60%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect/builds/6588
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9009983210291207344


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

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

Hi Peng, could you take a look at look at this report. It looks like your commit may have regressed performance here. Thanks 

My change is behind a flag. It is not enabled. I don't know how it can impact the performance. 

BTW, what is vm_working_set_final_size_total? Please clarify it?

Thanks Peng. I am not familiar with this benchmark just watching over the perfbots. The measure is going to be the working set as defined by the windows VM system for the process. It is possible this is not related to your change.

Does this need to compile for Windows at all (commit message refers to Chromebook)? Could it cause more code to run on Windows?

Moving this nonessential bug to the next milestone.

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

This has recovered.