Thanks for catching this! Will update the trybot threshold.

Curious where you found the alert threshold?

I didn't find exact alert threshold, but just one alert that fired at 15.8KiB, not sure if actual alert level is lower. I wouldn't be surprised though if it's just a simple 16000.

I found this repo but I haven't found the code for generating alerts: https://chromium.googlesource.com/catapult.git/+/master/dashboard/dashboard/alerts.py

+jparent@ Hi Julie, would you mind helping us find the threshold for the binary size perf alert?

cc'ed a few folks who might be able to help

In the group_report link in #0, click the alert, scroll through the tooltip, click "Debug alert":

https://chromeperf.appspot.com/debug_alert?test_path=ChromiumPerf/Android%20Builder%20Perf/resource_sizes%20(MonochromePublic.apk)/MonochromePublic.apk_Specifics/normalized%20apk%20size&rev=604323

Threshold configuration is currently:
{
  "max_window_size": 2, 
  "min_absolute_change": 16000, 
  "min_relative_change": 0, 
  "min_segment_size": 0
}

estevenson: please update that configuration as desired. Let me know if you run into any issues.

Changed to 16384 to match the trybot, thanks!

Reloading the page shows the new min_absolute_change as 16384, but when I click on "debug alert" again it's still showing as 16000 - anything else I need to do besides change the value and click "Update"?

Huh, it looks like that Update button was never wired up. :-/

/edit_anomaly_configs is only accessible to admins, so I changed the config for you there.

Great, thanks Ben!