Manual talk:Maxlag parameter

Latest comment: 3 years ago by GreenC in topic Nice value

Move to Manual: namespace?[edit]

Any objection to moving this page to Manual:Maxlag parameter? Tizio 16:06, 26 April 2007 (UTC)Reply

Usage question[edit]

Is it desired that bots should include the maxlag parameter on all requests, or only on those that entail editing the wiki contents? I.e., do read-only requests affect the replication lag? --Russ Blau 18:03, 13 December 2007 (UTC)Reply

According to API:Etiquette#Use maxlag parameter and this thread, non-interactive bots should always use the maxlag parameter, regardless of the kind of request. --Lucas Werkmeister (WMDE) (talk) 15:54, 9 July 2018 (UTC)Reply

200, not 503?[edit]

I'm getting a 200 OK, not a 503, from the English Wikipedia right now for maxlag warnings? See [1]. Jpatokal 22:49, 25 September 2011 (UTC)Reply

Nice value[edit]

Can someone please confirm that the nicest value is the lowest eg 1? Because to me it seems like a higher value like 10 or 20 seconds would be nicer. -- GreenC (talk) 23:57, 29 June 2020 (UTC)Reply

Usually yes, bots have maxlag settings in the meaning of maximum lag, over which bot pauses its work. The higher you set it, the more aggressive/invasive bot will be. The nicest is to pause your bot if lag > 1s, 5s is standard (recommended) value, when you pause your bot at 10s or 20s lag, it is more invasive. --Dvorapa (talk) 16:53, 30 June 2020 (UTC)Reply
Dvorapa, as far as I can tell, if you issue an API call with &maxlag=5 and the lag on the API server is > 5 then the API call will abort with an error message concerning max lag exceeded ie. the lag on the API server has exceeded the &maxlag= in the API call. How the bot reacts to that is up to the bot author - it might sleep and try again, or abort entirely., but it's not the same as the "Maxlag parameter" which is specific to the lag on the API server side. None of this has been fully explained in the docs. -- GreenC (talk) 01:02, 29 March 2021 (UTC)Reply