Our endpoint for counting the number of minor edits in a page's history is somewhat inefficient. We've put some work into keeping it from being too disruptive for the site, but we'd like to get to a good long-term solution.
Per T235572#5634376 @tstarling suggests that we:
- Add object cache to keep the value in cache
- Add a PoolCounter check to prevent too many calls to the endpoint