Manual:$wgJobQueueIncludeInMaxLagFactor
| Extensions: $wgJobQueueIncludeInMaxLagFactor | |
|---|---|
| Whether to include the number of jobs that are queued for the API's maxlag parameter. |
|
| Introduced in version: | 1.29.0 (Gerrit change 347320; git #de9f9bda) |
| Removed in version: | Still in use |
| Allowed values: | (boolean) |
| Default value: | false |
| Other settings: Alphabetical | By function | |
Whether to include the number of jobs that are queued for the API's maxlag parameter.
Details
[edit]The total number of jobs will be divided by this to get an estimated second of maxlag. Typically bots backoff at maxlag=5, so setting this to the max number of jobs that should be in your queue divided by 5 should have the effect of stopping bots once that limit is hit.