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

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


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

Win 7 Perf

rendering.desktop - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

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

📍 Found significant differences after each of 3 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/10e24e22e40000

Defer returning resources from display compositor by sunnyps@chromium.org
https://chromium.googlesource.com/chromium/src/+/5358dbe0785f91b2208e77853e6ff3691fc1d43e
tasks_per_frame_total_all: 39.53 → 40.7 (+1.173)

NUX: Move NUX backend code to chrome/browser/ui/webui/welcome by scottchen@chromium.org
https://chromium.googlesource.com/chromium/src/+/ea61398177d8de61681325395011610acfd3ad57
tasks_per_frame_total_all: 41.24 → No values

Revert "NUX: Move NUX backend code to chrome/browser/ui/webui/welcome" by keishi@chromium.org
https://chromium.googlesource.com/chromium/src/+/b553ee7cf218e38f7b747b8344878b7a44f6fe7c
tasks_per_frame_total_all: No values → 40.55

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

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

I just reverted a CL. sunnyps@'s change is more likely to be the related.

 Issue 893783  has been merged into this issue.

 Issue 893805  has been merged into this issue.