Xqt added a comment.
In T245144#5886173 <https://phabricator.wikimedia.org/T245144#5886173>, @Urbanecm wrote: > On the other hand, when I imagine a Retry-After change, the bots (complying with https://www.mediawiki.org/wiki/Manual:Maxlag_parameter, includes PWB) sleep for longer time, giving WDQS more time to recover. The number of new edits saved should be the same, given lag re-increases with the same speed. Not sure about other bots, but PWB seems to sleep for (at least) the recommended number of seconds, and then tries again. If the recommended number of seconds were higher, the bots should just edit slower, IMO. How pwb works with throttleling: - the http response header value `retry_after` is responsible for the delay after a maxlag has been triggered - The `retry_after` value was alway 5 s the last years. Therefore the current maxlag value was also taken into account for the wait cycle by 1/5 for the first try, 2/5 for the second try, 4/5 for the third, 8/5 for the forth 16/5 for the fifth etc. mut never less than retry_after value. - there is a put throttle for every api write access which 10 s by default but should never be below 5 by the most local bot policies - there is a minthrottle for every api read Access which is 0 by default i.e. there is no read throttleling at all. - if more than one bot is working simultaneously the times are lengthened **I guess the minthrottle should be activated for read access on wikidata too to avoid server overload** TASK DETAIL https://phabricator.wikimedia.org/T245144 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Xqt Cc: Xqt, Dvorapa, Ladsgroup, Multichill, Bugreporter, Ammarpad, Aklapper, Urbanecm, darthmon_wmde, Nandana, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer, _jensen, rosalieper, Scott_WUaS, Jonas, Wikidata-bugs, aude, Lydia_Pintscher, Mbch331
_______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
