Manual:$wgExpensiveParserFunctionLimit
| Parser: $wgExpensiveParserFunctionLimit | |
|---|---|
| Maximum number of calls per parse to expensive parser functions such as PAGESINCATEGORY. |
|
| Introduced in version: | 1.13.0 (r32932) |
| Removed in version: | still in use |
| Allowed values: | (integer) |
| Default value: | 100 |
| Other settings: Alphabetical | By function | |
Details
[edit]Maximum number of calls per parse to expensive parser functions such as PAGESINCATEGORY. Expensive parser functions include:
- {{#ifexist:}} (from Extension:ParserFunctions)
- {{PAGESINCATEGORY}}/{{PAGESINCAT}} (a Magic Word)
- {{PAGESIZE}} (a Magic Word)
- {{REVISIONUSER}} and {{REVISIONTIMESTAMP}} when used with the optional argument to specify a different page
- {{CASCADINGSOURCES}} (a Magic Word)
- Some Lua MediaWiki-related functions (see Lua reference manual), including
mw.incrementExpensiveFunctionCount()which can be used to manually mark a Lua code path as expensive. <syntaxhighlight>(since 1.39)- Search for
Parser::incrementExpensiveFunctionCount()calls to find more wikitext features that are considered expensive.
A limit report for the current page can be found as a comment in the HTML source of the page. Even without saving, the count for any wikitext can be checked by checking the html-source of the preview page for that wikitext.