Manual:Parser cache

The parser cache is responsible for caching the rendered output of a wiki page. It is the primary caching mechanism for serving page views in MediaWiki (not counting any web-cache such as Varnish in front of MediaWiki). The main ParserCache stores output of the latest revision of a page.

Metadata and Payload Data
The primary content of the parser cache is rendered output (HTML) generated from the page content (typically wikitext). In addition, the ParserOutput in the cache contains the following kinds of information:


 * Cache meta-data: this includes information about which revision the output was generated for, when it was generated, and when it should expire. In addition, ParserOutput records which options where used when generating the output (that is, which options the output varies on).
 * Derived data: this includes information about links and dependencies, e.g. which pages does the output link to, which templates were used in its creation, which images are included on the page. This also includes any special scripts or style sheets required to display the page, as well as arbitrary "page properties" that are to be places in the page_props table.
 * Extension data: extensions can attach arbitrary data to the  object which will be cached along with the rendered output. This provides extensions with a way to pass information from code that is executed during parsing to code that is executed during page display, typically during a later request.

Since MediaWiki version 1.36, data stored in the parser cache is encoded as JSON. For this reason, only objects in the  interface can be stored in the cache, e.g. as extension data. Earlier versions of MediaWiki relied on PHP's built-in serialization mechanism and allowed for arbitrary objects to be stored, at the cost of robustness and security (see T161647).

Cache Structure and Key Space
The ParserCache supports storing multiple  objects for each page, based on the   used when generating the output. To avoid duplicating cache entries by varying the cache key on options that were not actually used, a two-tiered system is employed:

The first tier is keyed by the page ID and stores, which contains information about cache expiration and the list of   used during the parse of the page. For example, if only the dateformat and userlang options were accessed by the parser when producing output for the page, this fact will be stored in the metadata cache.

The second tier of the cache contains the actual  objects. The key for the second tier is constructed from the page ID and values of those ParserOptions used during a page parse which affected the output. Upon cache lookup, the list of used option names is retrieved from the first tier, and only the values of those options are hashed together with the page ID to produce a key, while the rest of the options are ignored. Following the example above where only the dateformat and userlang options affected the output for the page, the key will look like. Thus any cache lookup with  and   will hit the same cache entry regardless of the values of the rest of the options, since we know from the information in the first cache tier that they were not accessed during a parse and thus did not change the output.

Population, Invalidation, Expiry, and Eviction
The parser cache serves as a semi-permanent store of a wiki's content as seen by readers. The default ("canonical") rendering of the page is generated immediately when the page is edited, or when any template or other dependency of the output changes (see LinksUpdate). Output using different options is generated and cached on demand.

The parser cache uses a passive invalidation model based on timestamps: When the content of a page changes, a timestamp is updated in the database (specifically, the  field in the   table). If the cached ParserOutput is older than this timestamp, it is considered outdated (stale). Outdated content may still be served to the user depending on context.

In addition to invalidation, entries in the parser cache will expire after a set period (see Manual:$wgParserCacheExpireTime). The expiry time can be lowered on a per-page basis, depending on the content of the page by calling  on the   object. Extensions that allow the inclusion of dynamic content may use this to ensure that the dynamic content is re-evaluated at an appropriate rate. Beyond this, the Manual:$wgCacheEpoch setting provides a way to expire all cache entries older than a specific point in time, e.g. to ensure that changes in the site's setup or configuration take effect.

Depending on the configuration of the cache's storage backend (see Manual:$wgParserCacheType), cache entries may or may not be evicted from the cache prior to expiry, or may be expunged from storage once expired. In general, the parser cache should be configured to ensure a very good hit rate, since it directly affects the time it takes to load a page for reading.

For information about the setup of the parser cache backend for Wikimedia sites, see wikitech:Parser_cache.

ParserCache Factory
Since MediaWiki version 1.36, it is possible to have multiple  instances side by side. This can be used in situations in which entirely different kinds of output need to be stored for each page, or the output varies on factors beyond what is covered by. One example for this is the FlaggedRevs extension which uses a separate ParserCache to store the rendered output of the "stable" version of each page, rather than the current one. Another example is migration to a different parser (such as Parsoid), which makes it necessary for a while to have caches for the output of the new as well as of the old parser.

Different  instances are managed by the   which can be obtained from.

Old Revision Output Cache
The main ParserCache only covers the latest revision of a page, but under some conditions it is desirable to also have caching for the rendered output of old revisions of a page. Since MediaWiki version 1.36, a cache similar to  exists for old revisions: the. The intent of this cache is to protect against load spikes caused by certain old revisions being viewed by a large number of users, typically due to an external "deep" link to that revision. For this reason, this cache is usually configured with a short expiry time (see Manual:$wgOldRevisionParserCacheExpireTime). Low hit rates are expected under normal operations, since it is generally rare for the same old revision to be visited a lot in a short time span.

As with, instances  of   are managed by the.

Configuration
See Manual:Configuration_settings