Krinkle added a comment.
@Magnus It is well-known currently that MediaWiki exposes many powerful API that we do not support to perform well, but allow regardless as a convenience service. If we were stricter about response times for all features, we'd probably just turn many of them off and limit the capabilities of those APIs until and unless the amount of resources required to make them work reliably fast is justified. I expect the maintainers of this API to have tested the supported and encouraged use cases and to know whether they are fast. I haven't personally looked at the p99 for this particular API, but from experience in other endpoints, it tends to be extreme cases that we'd be very unlikely to support with fast responses. But if they haven't in a while, it's certainly worth looking at those again from time to time. Meanwhile, do let us know if you find a response with a slow value recorded in the Backend-Timing header. You can use this to see whether the time was spent on the web server or in transportation/routing. If it's in routing that still doesn't mean it's outside Wikimedia control, we do influence a lot of the routes between DCs and for ISPs/peering and BGP stuff. It just helps narrow it down. TASK DETAIL https://phabricator.wikimedia.org/T226084 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Krinkle Cc: Tgr, Krinkle, jcrespo, Addshore, alaa_wmde, Lea_Lacroix_WMDE, WMDE-leszek, Aklapper, Magnus, darthmon_wmde, Nandana, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer, _jensen, rosalieper, Jonas, Wikidata-bugs, aude, Lydia_Pintscher, Mbch331
_______________________________________________ Wikidata-bugs mailing list Wikidata-bugs@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
