Wiki source code of Performances
Version 8.1 by Vincent Massol on 2008/01/18
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
3.1 | 1 | #startfloatingbox() |
| 2 | *Contents* | ||
| 3 | #toc ("2" "3" "") | ||
| 4 | #endfloatingbox() | ||
| 5 | |||
| |
1.1 | 6 | 1 Performances |
| 7 | |||
| 8 | 1.1 Database Indexes | ||
| 9 | |||
| 10 | Make sure you've set [Database indexes>Database Administration>]. This is especially important when you start having lots of documents. | ||
| 11 | |||
| 12 | 1.1 Panels | ||
| 13 | |||
| 14 | Some Panels take more resources than others. For example the Navigation panel should NOT be used for wikis with a lot of documents since it displays all documents in the wiki. In the future that Panel should be improve for performances but that's not the case right. Originally this Panel was only meant as a starting point. A better approach is to use a Quick Links Panel as we've now set up in the default XWiki Enterprise wiki version 1.1 (we've removed the default usage of the Navigation Panel in that version). | ||
| 15 | |||
| |
1.2 | 16 | 1.1 Statistics |
| |
1.1 | 17 | |
| |
1.2 | 18 | The statistics module is off by default since it's quite Database intensive. If you don't need it you should turn it off. |
| 19 | |||
 |
7.1 | 20 | 1.1 Monitoring |
| 21 | |||
| 22 | More a developer-oriented feature, XWiki can monitor its own code, reporting the time spent for each sub-component activated during a request. While the monitoring code isn't time consuming, it increases the memory consumption a bit, and the create/start/stop/log/destroy calls are spread all around the code, so you will save a lot of method calls by disabling this. You can do that by setting the following line in <tt>xwiki.cfg</tt>: | ||
| 23 | {code:null} | ||
| 24 | xwiki.monitor=0 | ||
| 25 | {code} | ||
| 26 | |||
| |
1.2 | 27 | 1.1 Cache sizes |
| 28 | |||
| |
8.1 | 29 | Tune the document cache in <tt>xwiki.cfg</tt>. The value depends on how much memory you have. The higher the better. A good reasonable value is 1000. |
| |
2.1 | 30 | |
| |
8.1 | 31 | {code:none} |
| 32 | xwiki.store.cache.capacity=1000 | ||
| 33 | {code} | ||
| 34 | |||
| |
2.1 | 35 | 1.1 Rendering cache |
| 36 | |||
| 37 | Some pages are complex to render (they may aggregate outside data for example or do complex and slow queries). For these pages you can add the following to their content to cache them after they are rendered. For example to cache the rendered content for 60 seconds you would add: | ||
| 38 | |||
| 39 | {code:none} | ||
| 40 | $context.setCacheDuration(60) | ||
| 41 | {code} | ||
| 42 | |||
| |
4.1 | 43 | 1.1 Backlinks |
| 44 | |||
| |
5.1 | 45 | While a pretty neat feature, keeping track of the backlinks has a medium impact on the document saving time and a minor impact on the document loading time. If you feel that your wiki does not need backlinks, you can safely disable them with the following line in <tt>xwiki.cfg</tt>: |
| |
4.1 | 46 | {code:none} |
| 47 | xwiki.backlinks=0 | ||
| 48 | {code} | ||
| |
5.1 | 49 | |
| 50 | 1.1 Versioning | ||
| 51 | |||
| 52 | One of the key features of any wiki system, versioning greatly affects the database size and the document update time. If you are sure your wiki does not need to keep track of all the changes and you will never need to revert documents to a previous version, then you can add the following line in <tt>xwiki.cfg</tt> | ||
| 53 | {code:none} | ||
| 54 | xwiki.store.versioning=0 | ||
| 55 | {code} | ||
| |
6.1 | 56 | |
| 57 | 1.1 Wiki syntax features | ||
| 58 | |||
| 59 | If you don't plan to use all of the wiki features, like the --strikethrough-- filter, the automatic http links filter, the SVG, Laszlo or style macros, you can disable them in <tt>xwiki-core-\*.jar/META-INF/services/com.xpn.xwiki.render.\*</tt>. The wiki rendering is the most costly operation in the rendering process, so any disabled feature counts. |
