Commons:Bots/Requests/Faebot

Faebot (talk · contribs)

Operator: Fæ (talk · contributions · Statistics · Recent activity · block log · User rights log · uploads · Global account information) (assign permissions)

This request does not change the current agreed scope for Faebot. Faebot is highly active and has been running on GLAM related tasks for 3.5 years, reaching nearly 3 million edits.

Bot's tasks for which permission is being sought: No new tasks, however the intention of this request is to remove or significantly reduce standard throttle limits for the account to help ensure that mass small housekeeping tasks such as intelligent re-categorization can happen in a more prompt and useful way. A related discussion was at Commons:Bots/Work_requests#Throttle_limits.

Normally supervised when testing then may be unsupervised for very large tasks, depending on the run time.

Automatic or manually assisted: Automatic

Edit type (e.g. Continuous, daily, one time run): Reduction of throttle limits would normally be for individual one-time jobs, comprising of housekeeping for various batch upload projects.

Maximum edit rate (e.g. edits per minute): This request is to unthrottle Faebot, or to allow run rates of at least 1 edit per second for simple mass tasks that it already has a long history of performing, such as (re)categorization, improving chosen licenses, multi-language fixes, renaming new uploads, repairing cross-links, fixing template issues or adding templates such as mass OTRS ticketing or changing agreed credits. On rare occasion these changes may need to touch over 100,000 files, so one key rationale for unthrottling is so that these bot-flagged changes happen quickly, rather than dragging on appearing in recent changes for a week or more if anyone is patrolling bot-edits.

More complex changes, such as the popular GLAM dashboard reports, will remain throttled at the standard maximum default rate of 10 seconds per edit. There is no intention of using significant (if any) parallel threads in these jobs/projects. For this reason any edits should remain a magnitude lower than can be seen when users run large jobs with the VFC and other tools.

Bot flag requested: (Y/N): N/A

Programming language(s): Python using pywikibot, both core and compat. This runs from both labs and client-side.

P.S. in creating this request I have overwritten the last request, which can be seen in the history. Fæ (talk) 19:48, 4 February 2016 (UTC)

Discussion

@Fæ: There is no throttle for the api (highapiratelimit is in botflag included). One (or moor) edit per second schould be "technically" possible (but not suggested). You can remove the pywikipediabot-trottel if you want to edit faster. There is mw:API:Etiquette and Commons:Bots#Bot speed. Best :-) --Steinsplitter (talk) 19:56, 4 February 2016 (UTC)

The only way I have read about doing this is to change -putthrottle:nn. Running this with nn=0 or 1 still gives me 10s/edit in practice. I presumed this was the way the bot account was set, is there something I'm overlooking in configuring this? --Fæ (talk) 20:10, 4 February 2016 (UTC)

Try to add put_throttle=nn (nn=second) to the user-config.py --Steinsplitter (talk) 20:13, 4 February 2016 (UTC)

Thanks, I have to sort out my paths a bit, but a similar hack does the job (a re-cat task is now achieving about 15 edits/min). I'd been assuming that the account had a higher throttle built-in for years, as the command-line parameter does not override the 10s default. Strange how things like basic config are so arcane. I'll take this request off the list shortly. --Fæ (talk) 20:27, 4 February 2016 (UTC)