Since T160692: Use poolcounter to limit number of connections to ores uwsgi has been deployed, some of our problematic strategies for querying ORES are coming back to bite us. E.g. the ArticleQuality.js gadget (T201927: Implement ORES gadget for article quality) sends too many parallel requests to the ORES service and it is then throttled. This has left the gadget in a broken state.
So! We need to implement a better strategy for batching requests to ORES. There's a related task for developing an ORES client T201691: Implement JS ORES client in mw-ORES extension. Let this task be the ground work for a more general client.