Handbuch:$wgParserCacheType

This page is a translated version of the page Manual:$wgParserCacheType and the translation is 23% complete.
Outdated translations are marked like this.
Parser-Cache: $wgParserCacheType
Parsercache-Einstellung
Eingeführt in Version:1.5.0
Entfernt in Version:Weiterhin vorhanden
Erlaubte Werte:(Einer der CACHE-Konstanten) siehe unten
Standardwert:CACHE_ANYTHING

Details

The cache type for storing page content HTML (e.g. parsed from wikitext).

Parsing wikitext is considered an expensive operation. It is recommended to give your parser cache plenty of storage space, such that long tail cache hits are possible.

The default parser cache backend (when MainCacheType is left to CACHE_NONE) is effectively CACHE_DB (SqlBagOStuff). If you set up a main cache type such as memcached, it is recommended to set this explicitly to CACHE_DB.

Here are the available cache constants, as defined in Defines.php

  • CACHE_ANYTHING - Use anything, as long as it works
  • CACHE_NONE - Do not cache
  • CACHE_DB - Store cache objects in the DB
  • CACHE_MEMCACHED - memcached, must specify servers in Handbuch:$wgMemCachedServers
  • CACHE_ACCEL - APC, or WinCache, whichever is available, in this order. Determined by the function "ObjectCache::newAccelerator".

Anmerkung

Advice for large wiki farms:

  • Consider allocating a dedicated database to ParserCache. Register it in $wgObjectCaches and point $wgParserCacheType to it.
  • Consider using MultiWriteBagOStuff to add a higher tier with Memcached in front of the lower database tier.
  • Consider setting 'purgePeriod' => 0 in the dedicated SqlBagOStuff entry in $wgObjectCaches. This disables the automatic purging of expired rows (which would normally happen in the background of write requests). You can then schedule the purgeParserCache.php script to e.g. once a day prune expired rows from the a dedicated maintenance server.


Siehe auch