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

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


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

Android Nexus6 WebView Perf

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

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

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

Include anchor element metrics that differ from one from document URL by tbansal@chromium.org
https://chromium.googlesource.com/chromium/src/+/290d578e4aa4458206ceb564744ef3d7c43c7c9a
console:error:all: 142.5 → No values

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

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

The CL that triggered this alert is behind a finch experiment. As of now, the experiment is not enabled on Stable channel. Currently, the code is running in the dry run mode: i.e., there is some computational overhead involved, but the feature does not take any actual action (besides recording metrics).

Before we start ramping up on Stable, we plan to move it out of the dry run mode. At that point, hopefully, the actions taken by the experiment would more than compensate the computational overhead.

Since the experiment is behind finch, and we are going to compare the usual performance and heartbeat metrics against the Control group (e.g., time to interactive, Event.Latency.*), I am inclined to close this as WontFix since there is nothing really actionable here.