|Other languages:||English • 한국어|
This page provides an overview of different ways to improve the performance of MediaWiki.
MediaWiki is capable of scaling to meet the needs of large wiki farms such as those of Wikimedia Foundation, Wikitravel and Wikia and can take advantage of a wide number of methods including multiple load-balanced database servers, memcached object caching, Varnish caches (see Manual:Varnish caching) and multiple application servers. For most smaller installations, this is overkill though, and simply enabling object caching and optimizing PHP performance should suffice.
Short version: We recommend bytecode cache for PHP, APCu as local object cache, Memcached for main cache; this is what the Wikimedia Foundation uses for Wikipedia et al.
In some cases, over-caching at too many levels may degrade performance.
Quick start with Puppet
Most of the tweaks on this page have been collected in a puppet manifest (puppet/modules/role/manifests/simple_performant.pp and puppet/modules/role/manifests/simple_miser.pp). If you install Puppet, you can apply them to your server with a single command.
- 1 Context
- 2 Quick start
- 3 PHP
- 4 Object caching
- 5 Page view caching
- 6 Web server
- 7 Configuration settings
- 8 Database configuration
- 9 Benchmarking
- 10 See also
- 11 References
PHP works by compiling a PHP file into bytecode and then executing that bytecode. The process of compiling a large application such as MediaWiki takes considerable time. PHP accelerators work by storing the compiled bytecode and executing it directly reducing the time spent compiling code.
OPcache is included in PHP 5.5.0 and later and the recommended accelerator for MediaWiki. Other supported op code caches are: WinCache.
Opcode caches store the compiled output of PHP scripts, greatly reducing the amount of time needed to run a script multiple times. MediaWiki does not need to be configured to do PHP bytecode caching and will "just work" once installed and enabled them.
HipHop Virtual Machine is a JIT for Hack developed by, and used in production at Facebook. HHVM is not recommended for MediaWiki as it diverges from PHP7/ The WMF is actively dropping support for HHVM and moving to PHP7.
For more information about local server, main cache and other cache interfaces, see Manual:Caching.
This interface is used for lightweight caching directly on the web server. This interface is expected to persist stored values across web requests.
Presence of a supported backend is automatically detected by MediaWiki. No configuration necessary.
apc.php is bundled with the APC package which can be used to inspect the status of the cache, and also examine the contents of the user cache to verify that MediaWiki is correctly using it.
This interface is used as the main object cache for larger objects.
The main cache is disabled by default and needs to be configured manually. To enable it, set
$wgMainCacheType to a key in
$wgObjectCaches. There are preconfigured interfaces for Memcached, APC, and MySQL. You can configure additional backends via
$wgObjectCaches (e.g. for Redis).
$wgMainCacheType = CACHE_NONE;
Single web server
If you have APC installed is strongly recommended to use that by setting the following in LocalSettings.php:
$wgMainCacheType = CACHE_ACCEL;
When using APC with limited RAM and no Memcached or other object cache, objects may be evicted too often due to the size of parser output cache. Consider overriding
$wgParserCacheType to CACHE_DB. This will move those keys to the database instead.
If you can't use APC, consider installing memcached (will require at least 80MB or more of RAM). While installing Memcached is considerably more complicated, it is very effective.
If neither APC or Memcached is an option, you can fallback to storing the object cache in your MySQL database. The following preset will do that:
$wgMainCacheType = CACHE_DB;
Multiple web servers
If your MediaWiki site is served by multiple web servers, you should use a central Memcached server. Detailed instructions are on the memcached page.
The APC object cache is not suitable as the main cache for use in environments where multiple web servers are used, as this cache is expected to exist in one place only. Using it differently may cause keys to become stale when values change. It is still recommended that you still APC for use by local-server caches, which MediaWiki will take advantage of it where possible.
By default, interface message translations are cached in the l10n cache database table. Ensure $wgCacheDirectory in LocalSettings.php is set to a valid path to use a local caching instead. See Localisation#Caching for more details.
Page view caching
Page view caching increases performance tremendously for anonymous (not logged-in) users. It does not affect performance for logged-in users.
Simply put, HTTP accelerators (or "caching proxies") store copies of pages sent out by the web server. When a cached page is requested a second time, the proxy serves up the copy instead of passing the request on to the web server. This can tremendously reduce the load on the MediaWiki web server. When a page is updated, the copy is removed from the accelerator's cache through a purge.
Use Varnish as cache proxy, your leverage any built-in support your web server may have through a plug-in or configuration option.
- See Manual:File cache for main article about this.
In absence of a caching proxy or HTTP accelerator, MediaWiki can optionally use the file system to store the output of rendered pages. For larger sites, using an external cache like Varnish is preferable to using the file cache.
- if you use Apache as web server, use PHP-FPM, not mod_php. PHP-FPM optimizes re-use of PHP processes.
- switch Apache to use the event MPM instead of the prefork MPM.
- adjust robots.txt to disallow bots from crawling history pages. This decreases general server load.
- HTTP/2 protocol can help, even with ResourceLoader.
MediaWiki uses composer for solving dependencies. By default it search all packages in /vendor folder for classes need autoload. It`s a realtime operation and it supports caching only at bytecode level. But you can set composer for using static list of autoload classes, which will make your wiki faster.
Open console in /vendor dir and simply enter:
composer update --no-dev
But you should repeat that procedure on every vendor library update.
For a heavy concurrent write load, InnoDB is essential. In MediaWiki 1.24 and earlier, set
$wgAntiLockFlags = ALF_NO_LINK_LOCK | ALF_NO_BLOCK_LOCK; to reduce lock contention, at the expense of introducing occasional inconsistencies. Use memcached, not the default MySQL-based object cache.
See below for some DB configuration tricks. You can also try and run the mysql-tuning-primer script to get some quick statistics and suggestions.
The database software and web server software will start to fight over RAM on busy MediaWiki installations that are hosted on a single server. If your wiki has a consistent traffic, a logical step, once other performance optimizations have been made (and cache serves most of the content), is to put the database and web server on separate servers (or, in some cases, multiple separate servers, starting with a slave.) Also:
- check that MySQL has query cache enabled and enough memory;
- give most memory to innodb_buffer_pool;
- add cores for MySQL if maxed out at peak times;
- give memcached even more RAM for in-memory cache.
Some tools can help quickly evaluate the effects of performance tuning.
- http://webpagetest.org is "real life" testing, commanded in your browser.
- ab is a command line tool which quickly produces some nice stats.
- http://dammit.lt/2007/01/26/mediawiki-performance-tuning/ : APC and a few simple settings that boost performance
- More extensive changes, sacrificing some functionality
- User:Ilmari Karonen/Performance tuning, focusing on small wikis
- Use cases
- For developers: