Changes
→Why the job queue exists
{{h:h|system admin toc}}[[Category:System admin handbook]]
In MediaWiki 1.6, a '''job queue''' was introduced, to perform long-running tasks asynchronously. The job queue is designed to hold many short tasks. You can view the length of the job queue by visiting [[Special:Statistics]] on most 1.6 wikis. By default, each time a request runs, one job is taken from the job queue and executed. If the performance burden of this is too great, you can reduce $wgJobRunRate by putting something like this in your LocalSettings.php:
:<tt>$wgJobRunRate = 0.01;</tt>
You can also execute the job queue from the command line, by running <tt>maintenance/runJobs.php</tt>.
==Why the job queue exists==
===Updating links tables when a template changes===
MediaWiki 1.6 adds a job to the job queue for each article using the template. Each job is a command to read an article, expand any templates, and update the link table accordingly. So null edits are no longer necessary, although it may take a while for big operations to complete.
===HTML cache invalidation===
A wider class of operations can result in invalidation of the HTML cache for a large number of pages:
* Changing an image (all the thumbnails have to be re-rendered, and their sizes recalculated)
* Deleting a page (all the links to it from other pages need to change from blue to red)
* Creating a page (like above, but from red to blue)
* Changing a template (all the pages that transclude the template need updating)
Except for template changes, these operations do not invalidate the links tables, but they do invalidate the HTML cache of all pages linking to that page, or using that image. Invalidating the cache of a page is a short operation, it only requires updating a single database field and sending a multicast packet to clear the squid caches. But if there are more than about 1000 to do, it takes a long time. By default, jobs are added when more than 500 pages need to be invalidated, one job per 500 operations.
In MediaWiki 1.6, a '''job queue''' was introduced, to perform long-running tasks asynchronously. The job queue is designed to hold many short tasks. You can view the length of the job queue by visiting [[Special:Statistics]] on most 1.6 wikis. By default, each time a request runs, one job is taken from the job queue and executed. If the performance burden of this is too great, you can reduce $wgJobRunRate by putting something like this in your LocalSettings.php:
:<tt>$wgJobRunRate = 0.01;</tt>
You can also execute the job queue from the command line, by running <tt>maintenance/runJobs.php</tt>.
==Why the job queue exists==
===Updating links tables when a template changes===
MediaWiki 1.6 adds a job to the job queue for each article using the template. Each job is a command to read an article, expand any templates, and update the link table accordingly. So null edits are no longer necessary, although it may take a while for big operations to complete.
===HTML cache invalidation===
A wider class of operations can result in invalidation of the HTML cache for a large number of pages:
* Changing an image (all the thumbnails have to be re-rendered, and their sizes recalculated)
* Deleting a page (all the links to it from other pages need to change from blue to red)
* Creating a page (like above, but from red to blue)
* Changing a template (all the pages that transclude the template need updating)
Except for template changes, these operations do not invalidate the links tables, but they do invalidate the HTML cache of all pages linking to that page, or using that image. Invalidating the cache of a page is a short operation, it only requires updating a single database field and sending a multicast packet to clear the squid caches. But if there are more than about 1000 to do, it takes a long time. By default, jobs are added when more than 500 pages need to be invalidated, one job per 500 operations.
