Manual talk:$wgExpensiveParserFunctionLimit

Which functions?
Besides PAGESINCATEGORY, and #ifexist:, are there any other expensive parser functions? And if there are, should they be listed on this page? Timeroot 02:32, 24 January 2009 (UTC)

Magic word for this variable?
Is there a  that displays $wgExpensiveParserFunctionLimit (the way, e.g.,   displays $wgServer)?—msh210@enwikt 21:19, 12 February 2009 (UTC)
 * Nikerabbit has informed me on IRC that the answer is no.—msh210@enwikt 20:09, 17 February 2009 (UTC)

Question
Where is the page with the variable on it?--Launchballer 11:12, 29 August 2009 (UTC)

What if logically not executed
Does the counter add one when the expensive parser function is logically not executed? E.g. when used within a cheap conditional function like this:

 

If it does add, I might program differently (for other reasons, including simplicity). If not, it might be worth complicating the program (by doing more cheap conditions in outer functions). -DePiep 13:34, 27 August 2010 (UTC) Improving example, sp -DePiep 13:53, 27 August 2010 (UTC)


 * Testing:


 * It does not, as you can see in the html-source of this section: Preprocessor node count: 8/1000000 Post-expand include size: 8/2048000 bytes Template argument size: 0/2048000 bytes Expensive parser function count: 0/500.--Patrick 11:27, 6 September 2010 (UTC)


 * The syntax above is wrong, so it is not a valid test.
 * Let's try again, and also use a magic word to ensure that the test is not affected by any optimisation of an always-true expression:

  
 * Testing: 
 * And the resulting source code still shows zero expensive functions:


 * So the previous conclusion remains correct: a function only counts towards the limit if it is in the applicable logic path.
 * — Richardguk (talk) 13:49, 22 August 2012 (UTC)