See also T173121

Small correction/clarification on "this was found to generate too much load" as an ops, I interpret load as throughput/backlog work. The insertion [load] itself was not the problem (the spikes on inserts were too large, but something that could be smoothed); the problem lies in the proportion of wb-originated changes vs. others and the size of the recentchanges table itself. Literally, issues could be solved by making the 2 million different query patterns of recentchanges better, but I am going to assume that is more difficult than changing the wb rows behaviour :-).

The idea is a more accurate phrasing would be "this causes some recentchanges and watchlist-related queries to have >60 seconds of latency and the table became operationaly unmaintainable for some wikis".