Alert limitation discussion: Maximum number of alerts to display in UI

We currently show all possible alerts firing. There is a limit at which we can reasonably load and display all these alerts, but we're not sure what that value is.

From a bandwidth perspective:
From @beorn7

And one other aspect: If I'm on-call on the road, I sometimes need to work with low-bandwidth (e.g. shared crappy WiFi) and/or very expensive connection to the internet (e.g. tethering my phone). Even if thousands of alerts load fine with a broadband connection, and the browser on my 16GiB laptop is fine handling that, it might be very inconvenient in a situation like the above, where the first thing I do might be to look at the AM landing page (perhaps even on the browser of my smallish mobile phone).

Although the links from an alert notification include filters to reduce the number of results shown, a mass outage could still affect many instances, which might greatly slow the ability to load.

I personally think if you're on call you should probably stay somewhere that has access to fast, reliable internet, so I'm not proposing any solution to this at the moment, just documenting.

No files, tests, or entry points are mentioned. First clarify whether the project should cap the number of alerts displayed, then define the limit and the expected behavior for large alert sets and low-bandwidth connections.