Anomaly threshold configuration descriptions are here: https://cs.chromium.org/chromium/infra/appengine/findit/first_party/perf_dashboard/find_change_points.py?q=min_relative_change&sq=package:chromium&dr=C&l=34

Page for editing configs is here: https://chromeperf.appspot.com/edit_anomaly_configs (requires admin)

Current alerting configuration (which results to alert on) is here:
https://chromeperf.appspot.com/edit_sheriffs (requires admin)

Setting the following configuration:
----
{
  "min_relative_change": 0.10000000000000001
}
----
----
ChromiumPerf/*/media_perftests/*
ChromiumPerf/*/media_perftests/*/*
----

It seems to have worked.

AFAICT, this will make it so that the median values before compared with after will have to change at least 10%. That will prevent alerts like  issue 803517 .

(I copied this config from V8-noisy config.)

Happy to configure it with other values instead. 15%? 20%? We could also increase things like min_segment_size ( https://cs.chromium.org/chromium/infra/appengine/findit/first_party/perf_dashboard/find_change_points.py?q=min_relative_change&sq=package:chromium&dr=C&l=34 ) and multiple_of_std_dev to make it so that alerts only fire for sustained increases.

Feel free to re-open with any suggestions.

Ugh, wish it didn't keep switching to my @google.com account.

Fixed.