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

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


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

mac-10_13_laptop_high_end-perf

system_health.memory_desktop - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks

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

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/13277845140000

[TaskScheduler]: Disable MergeBlockingNonBlockingPools from fieldtrial_testing_config. by etiennep@chromium.org
https://chromium.googlesource.com/chromium/src/+/ad3c94a2279bd7584003990858339a94f69a838b
memory:chrome:all_processes:reported_by_chrome:skia:effective_size: 4.185e+06 → 9.486e+06 (+5.301e+06)

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

Benchmark documentation link:
  https://bit.ly/system-health-benchmarks

Issue 915757 has been merged into this issue.

Issue 916136 has been merged into this issue.

 Issue 916573  has been merged into this issue.

Issue 916453 has been merged into this issue.

All regressions seems related to disabling MergeBlockingNonBlockingPools feature from test config. That feature was already disabled on stable, so it is not affected by the regressions. 
Marking this bug as WontFix, though we can consider these regressions as improvement once we enable the feature again soon.

 Issue 917256  has been merged into this issue.

 Issue 916127  has been merged into this issue.

 Issue 917257  has been merged into this issue.