| Extensions: $wgJobBackoffThrottling | |
|---|---|
| Number of times work items of a job type can be run per second. |
|
| Introduced in version: | 1.23.0 (Gerrit change 103190; git #e8cb2073) |
| Removed in version: | still in use |
| Allowed values: | (number >= 0) |
| Default value: | [] |
| Other settings: Alphabetical | By function | |
Details
Number of work items of a given job type to perform per second.
What exactly a "work item" means is up to the job; it just has to return the number of them in Job::workItemCount().
For example, it could mean the number of pages updated for a job which does batch updates.
However, this setting won't limit the number of pages updated in one job run (which is controlled by $wgUpdateRowsPerJob).
Instead, it will throttle new executions of that job type.
Whenever a job of the given type gets executed, no jobs of the same type will be started in the next ( work item count / backoff throttling ) seconds.
This only affects jobs started by maintenance/runJobs.php (as opposed to $wgJobRunRate which only affects job started by web requests).
Example
$wgJobBackoffThrottling['htmlCacheUpdate'] = 5;
See also
- Manual:Job queue
- Manual:$wgJobRunRate
- Manual:$wgUpdateRowsPerJob
This article is issued from Mediawiki. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.