Background: [[d:User_talk:Legoktm#I_requested_a_block_for_Legobot]]

My bot was blocked for editing too fast and heavily increasing the lag for the dispatcher. Normally this wouldn't have been an issue on any other project since maxlag is all you need to worry about, except that on Wikidata has dispatcher lag.

I think the best way to fix this going forwards would be to either:
*Include dispatcher lag into maxlag
*Make dispatch lag it's own thing (&dispatchlag=1000)

For the time being, it would be nice if we could at least access the lag via the API, maybe in meta=siteinfo? (https://www.wikidata.org/w/api.php?action=query&meta=siteinfo&format=jsonfm)

I personally think making it it's own parameter is the best, since the scale of dispatch lag is very different than maxlag, and that there's no need to stop "normal bots" (an archivebot, anything non-wikidata related) from editing if dispatcher lag is high, however if you include it in with maxlag, there's no need to update existing frameworks.

Version: unspecified
Severity: major
Whiteboard: u=dev c=backend p=0
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=46642
https://bugzilla.wikimedia.org/show_bug.cgi?id=45892
https://bugzilla.wikimedia.org/show_bug.cgi?id=48140