GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Main page
  • Contents
  • Current events
  • Random article
  • About Wikipedia
  • Contact us
  • Help
  • Learn to edit
  • Community portal
  • Recent changes
  • Upload file
  • Special pages
  • Search
  • Donate

This view

  • Original page
  • New address

GeezerVison is showing en.wikipedia.org — Help:Job queue - Wikipedia

"WP:QUEUE" redirects here. For the "did you know" queue, see Template:Did you know/Queue.
This is an information page.
It is not a Wikipedia policy or guideline; rather, its purpose is to explain certain aspects of Wikipedia's norms, customs, technicalities, or practices. It may reflect varying levels of consensus.

In MediaWiki 1.6 (released in 2006), a job queue was introduced to perform long-running tasks asynchronously. The job queue is designed to hold many short tasks using batch processing.

Updating links tables when a template changes

MediaWiki 1.6 adds a job to the job queue for each article using a template. Each job is a command to read an article, expand any templates, and update the pagelinks table accordingly. So null edits are no longer necessary, although it may take a while for big operations to complete. This can help to ease strain on users.

HTML cache invalidation

A wider class of operations can cause 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 or undeleting 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 and uploading a not previously existing file, 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 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.

Typical values

The factual accuracy of parts of this help page (those related to section) may be compromised due to out-of-date information. The reason given is: The job queue is frequently at zero jobs.. Please help update this help page to reflect recent events or newly available information. Relevant discussion may be found on the talk page. (September 2026)

During a period of low loads, the job queue might be zero. At Wikimedia, the job queue is, in practice, almost never zero. In off-peak hours, it might be a few hundred to a thousand. During a busy day, it might be a few hundred thousand (values of several million are no cause for alarm), but it can quickly fluctuate by 10% or more.[1] Furthermore, several servers will have different estimates for this value so apparently more varying fluctuations can also be seen.

As of MediaWiki 1.17, job queue length can be retrieved via the API at https://en.wikipedia.org/w/api.php?action=query&meta=siteinfo&siprop=statistics (it is shown on the line labeled "jobs").[2] On Wikipedia this value can come from one of several servers (three as of 2009) and so may fluctuate significantly.

See also

  • mw:Redis
  • mw:Manual:Job queue

References

  1. ↑ "So what's in the job queue anyway?". brionv. 2008-04-22. Archived from the original on 2019-04-04. Retrieved 2019-10-14.
  2. ↑ "mw:Manual:Job queue#Special:Statistics". MediaWiki. Archived from the original on 2024-06-07. Retrieved 2024-06-07.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Help:Job_queue&oldid=1376378568"
Categories:
  • Wikipedia information pages
  • Wikipedia link help
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.