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

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


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

linux-perf
mac-10_12_laptop_low_end-perf
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/15b277d4540000

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/15b277d4540000

All of the runs failed. The most common error (20/20 runs) was:
ReadValueError: Could not find values matching: {'story': u'load:search:taobao', 'tir_label': u'load_search', 'histogram': u'memory:chrome:all_processes:reported_by_chrome:cc:effective_size'}

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

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

Reland [Optimize TaskQueueSelector] by alexclarke@chromium.org
https://chromium.googlesource.com/chromium/src/+/0c17bc4823f8506061a7f20935f95f0d71d4ad5c
memory:chrome:all_processes:reported_by_chrome:cc:effective_size: 1.837e+07 → 2.406e+07 (+5.694e+06)

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

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