Other parameters: Difference between revisions

No edit summary
Line 173:
{{DPL Parameter
|name = allowcachedresults
|purpose= allowCache delivery ofquery results basedto improve performance keep servers from oncrashing cachedunder databasehigh contentsload.
}}
 
Syntax:
 
<code>allowcachedresults=<i>true | false | yes+warn</i></code>
 
Explanation:
 
Default: true
Default is FALSE, so normally DPL will disable the parser cache before it produces a result. Disabling the cache produces some extra server load but guarantees always correct results.
All queries are cached by default to reduce server load as generally articles do not change often enough to require updating every page load. If immediate updates are required every page load then set this parameter to false. The cache period is handled by the [[#cacheperiod]] parameter.
 
So, if you do not use this parameter you will always get a result which is based on the latest changes made on any articles. But in many cases you could have gotten the same result with using less server resources!
 
If you set 'allowcachedresults=true', the parser cache will be used. That means, your results might be a little bit outdated (usually one hour or so). But there are less resources used on the server side. You might want to experiment with that parameter and check the size of load reduction (i.e. gain in term of response time).
 
If you allow cached results you can still enforce DPL to produce a correct result via using "&action=purge" in the command line.
 
'yes+warn' will use the cache; in addition the result will contain a warning indicating that the result may be out-dated. This is achieved by including the template ''DPL Cache Warning'' into the result header. It is up to you to provide a useful text under that name, see e.g. [[Template:DPL Cache Warning]].
 
===reset===
Anonymous user