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

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


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

android-nexus5
android-nexus5X
android-nexus6
android-nexus7v2
android-one
android-webview-nexus6

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

Daniel: can you look into the benchmark runtime regression?

These are the new benchmarks being added.

Daniel: how many tests did you add? Our device budget is very constraint, so it would be great if you can look into reducing the runtime

Ok, I'll reduce the test count from 12 to 4 by removing some of our strategies, and it will definitely bring this time down. When do you need this done by?

This is affecting how soon people can get perf results, so the sooner you can address this the better. Fixing this in 2 weeks is reasonable to me.

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

[BlobStorage] Adding size configurations to perftests by dmurph@chromium.org
https://chromium.googlesource.com/chromium/src/+/1131391c410a6d01c584c4449accc7e1b1258b06

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

I think this is WAI, given that we changed the tests.

#9: please see #5 & #6

Sorry I didn't read the whole thread carefully and thank you for fixing my mistake!

 Issue 814250  has been merged into this issue.

Reduced the tests, just didn't put this bug in the cl number. Now we have only 4, and they are pretty small.