Last modified: 2010-05-06 16:58:57 UTC
Currently the limit for $wgExpensiveParserFunctionLimit is 500 at pt.wiktionary. We need this to be around 1000, which is still acceptable, because we currently have some 6 pages which issue between 500 and 800 calls.
On what basis are you asserting that 1000 is "still acceptable"? Surely that's a call for a sysadmin to make...
If you have just several pages that exceed this limit, fixing them would make much more sense.
Mike, as we do have only half a dozen pages in this situation, I believe that it is acceptable. We're just doubling up for these exceptions. Bare in mind I'm making this assertion uniquely for this wiki, and not Wikimedia-wide. Max, if they were fixable, I would fix them. :) Ideally, bug:22808 is the best solution: caching #ifexist's and/or not counting duplicates for the 500 threshold.
(In reply to comment #3) > Mike, as we do have only half a dozen pages in this situation If you have only a half-dozen pages, it isn't so much work to fix them.
Maybe you could provide the links to such pages and explain why they can't be made less expensive?
Example in the following category: http://pt.wiktionary.org/wiki/Categoria:P%C3%A1ginas_com_demasiadas_chamadas_a_fun%C3%A7%C3%B5es_exigentes As these pages have a lot of translations (in excess of 500) and each translation require an #ifexist, they are considered expensive, even if most of the #ifexist calls are duplicated (so, in fact, there are some 200/300 unique #ifexist calls). This is because the text of the language does not necessarily correspond to the link. This is accomplished with an call to #ifexist with a template parameter based on the language code. If that template exists, then it is used instead of the direct language name.
#ifexist should perform its queries as a linkbatch, but it would require a bit of work to move things around.
This is not needed anymore. I reformed the template logic behind the translations. Thanks nevertheless. (Hmmm, it seems I can only mark this bug as Assigned or Resolved. Isn't there a Delete/Drop/WontFix choice?)
Apparently it's fixed... WONTFIXED. Reopen if its not.
