Skip to Content

Wiki source code of Performance

Version 43.1 by Thomas Mortagne on 2015/01/17
Show last authors
1 {{box cssClass="floatinginfobox" title="**Contents**"}}
2 {{toc/}}
3 {{/box}}
4
5 Here are some tips to increase XWiki's performance.
6
7 = Slow random number generation on UNIX =
8
9 The library used for random number generation in Sun's JVM relies on /dev/random by default for UNIX platforms.
10
11 Although /dev/random is more secure, it's possible te use /dev/urandom if the default JVM configuration instead.
12
13 To determine if your operating system exhibits this behavior, try displaying a portion of the file from a shell prompt:
14
15 head -n 1 /dev/random
16
17 If the command returns immediately, you can use /dev/random as the default generator for SUN's JVM. If the command does not return immediately, use these steps to configure the JVM to use /dev/urandom:
18
19 1. Open the $JAVA_HOME/jre/lib/security/java.security file in a text editor.
20 2. Change the line:
21 {{code language="properties"}}
22 securerandom.source=file:/dev/random
23 {{/code}}
24 to read:
25 {{code language="properties"}}
26 securerandom.source=file:/dev/urandom
27 {{/code}}
28 3. Save your change and exit the text editor.
29
30 = Gzip compression and caching of static pages =
31
32 We're working on making these features part of the XWiki core (see [[XWIKI-2022>>http://jira.xwiki.org/jira/browse/XWIKI-2022]]). While waiting for this to be natively implemented, the recommended solution is to set up an Apache Web Server in front of your servlet container and install/configure the following modules:
33
34 * [[mod-deflate>>http://httpd.apache.org/docs/2.0/mod/mod_deflate.html]]
35 * [[mod-expire>>http://httpd.apache.org/docs/2.0/mod/mod_expires.html]]
36 * [[mod-proxy-ajp>>http://httpd.apache.org/docs/2.2/mod/mod_proxy_ajp.html]] (note that this depends on [[mod-proxy>>http://httpd.apache.org/docs/2.2/mod/mod_proxy.html]] that you also need to install)
37
38 Modify your Apache configuration file to load the different modules:
39
40 {{code language="none"}}
41 LoadModule expires_module /usr/lib/apache2/modules/mod_expires.so
42 LoadModule deflate_module /usr/lib/apache2/modules/mod_deflate.so
43 LoadModule proxy_module /usr/lib/apache2/modules/mod_proxy.so
44 # Depends: proxy
45 LoadModule proxy_ajp_module /usr/lib/apache2/modules/mod_proxy_ajp.so
46 {{/code}}
47
48 //Alternatively you can run the following commands as root (sudo)//
49
50 {{code language="bash"}}
51 a2enmod deflate
52 a2enmod proxy_ajp
53 a2enmod expires
54 {{/code}}
55
56 and configure your different modules as described below:
57
58 == Mod Deflate Configuration ==
59
60 {{code language="none"}}
61 vwwwpro-1:~# cat /etc/apache2/conf.d/deflate
62 <Location />
63 # Insert filter
64 SetOutputFilter DEFLATE
65
66 # Netscape 4.x has some problems...
67 BrowserMatch ^Mozilla/4 gzip-only-text/html
68
69 # Netscape 4.06-4.08 have some more problems
70 BrowserMatch ^Mozilla/4.0[678] no-gzip
71
72 # MSIE masquerades as Netscape, but it is fine
73 # BrowserMatch bMSIE !no-gzip !gzip-only-text/html
74
75 # NOTE: Due to a bug in mod_setenvif up to Apache 2.0.48
76 # the above regex won't work. You can use the following
77 # workaround to get the desired effect:
78 BrowserMatch bMSI[E] !no-gzip !gzip-only-text/html
79
80 # Don't compress images
81 SetEnvIfNoCase Request_URI .(?:gif|jpe?g|png)$ no-gzip dont-vary
82
83 # Make sure proxies don't deliver the wrong content
84 #Header append Vary User-Agent env=!dont-vary
85 </Location>
86 {{/code}}
87
88 //On debian apache2 the config file for deflate is located under /etc/apache2/mods-enabled/deflate.conf//
89
90 == Mod Expire Configuration ==
91
92 {{code language="none"}}
93 vwwwpro-1:~# cat /etc/apache2/conf.d/expires
94 <Location /xwiki/skins/>
95 ExpiresActive on
96 ExpiresDefault "access plus 1 day"
97 </Location>
98
99 <Location /xwiki/bin/skin/>
100 ExpiresActive on
101 ExpiresDefault "access plus 1 day"
102 </Location>
103 {{/code}}
104
105 == Mod Proxy AJP Configuration ==
106
107 {{code language="none"}}
108 ProxyRequests Off
109 <Proxy *>
110 Order deny,allow
111 Allow from all
112 </Proxy>
113 ProxyPreserveHost On
114 ProxyPass /xwiki ajp://192.168.1.181:8009/xwiki
115 {{/code}}
116
117 where ##ajp:~/~/192.168.1.181:8009/xwiki## is the internal address of your Servlet container where XWiki is running.
118
119 If you use Tomcat(7) you need to enable the ajp connector in the /etc/tomcat7/server.xml. Comment out the following line with adding {{code}}<!-- -->{{/code}}. //Maybe give a comment why you did it.//
120
121 {{code}}
122 <!-- disable to use ajp connector instead
123 <Connector port="8080" protocol="HTTP/1.1"
124 connectionTimeout="20000"
125 URIEncoding="UTF-8"
126 redirectPort="8443" />
127 -->
128 {{/code}}
129
130 Uncomment the following line by removing the {{code}}<!-- -->{{/code}} and add {{code}}URIEncoding="UTF-8"{{/code}} to it.Maybe give a comment too.
131
132 {{code}}
133 <!-- Activate ajp connector for apache proxy_ajp -->
134 <Connector port="8009" protocol="AJP/1.3" redirectPort="8443" URIEncoding="UTF-8"/>
135 {{/code}}
136
137 = Memory =
138
139 You need to configure your Servlet container so that XWiki has enough memory. You'll need to tune the value to your need. You should check the logs and see if there are any "out of memory" errors. Here are some good default values:
140
141 * Small installs: A minimum of 300MB of heap memory and 196MB of permGen (##-Xmx300m -XX:MaxPermSize=196m##)
142 * Medium installs: 512MB for the heap and 196MB of permGen (##-Xmx512m -XX:MaxPermSize=196m##)
143 * Large installs: 800MB for the heap and 196MB of permGen (##-Xmx800m -XX:MaxPermSize=196m##). Try not to ge beyond 1024MB since adding more memory means more GC time and thus lower performance.
144
145 {{warning}}
146 Note that storing attachments with the default (in database) storage mechanism is very memory intensive. See the [[administrators guide to attachments>>platform:AdminGuide.Attachments]] for more information about memory cost and the alternative filesystem based attachment store.
147
148 Also note that uploading a lot of pages can trigger out of memory (OOM) errors due to scheduled watchlist jobs. For example uploading 1 million pages will trigger OOM errors even when the JVM is configured to run with 2GB of heap space. For such kind of load we recommend to disable (unschedule) the Watchlist jobs (in ##/xwiki/bin/view/Scheduler/##) before uploading the pages.
149 {{/warning}}
150
151 For your information here are the values used for the xwiki.org site:
152
153 {{code}}
154 CATALINA_OPTS="-server -Xms800m -Xmx800m -XX:MaxPermSize=196m -Dfile.encoding=utf-8 -Djava.awt.headless=true -XX:+UseParallelGC -XX:MaxGCPauseMillis=100"
155 {{/code}}
156
157 = Database Indexes =
158
159 Make sure you've set [[Database indexes>>Database Administration]]. This is especially important when you start having lots of documents.
160
161 = Panels =
162
163 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 improved for performance but that's not the case right now. 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).
164
165 = Robots.txt =
166
167 If your wiki is open on the Internet, it'll be crawled by search robots (like GoogleBot, etc). They will call all the URLs and especially the ones that are resource hungry like exports (PDF/RTF). You need to protect against this. To do so configure a ##robots.txt## file like this one and put it in your webserver configuration:
168
169 {{code language="none"}}
170 User-agent: *
171 Disallow: /xwiki/bin/attach/
172 Disallow: /xwiki/bin/cancel/
173 Disallow: /xwiki/bin/commentadd/
174 Disallow: /xwiki/bin/delattachment/
175 Disallow: /xwiki/bin/delete/
176 Disallow: /xwiki/bin/dot/
177 Disallow: /xwiki/bin/download/
178 Disallow: /xwiki/bin/downloadrev/
179 Disallow: /xwiki/bin/edit/
180 Disallow: /xwiki/bin/export/
181 Disallow: /xwiki/bin/get/
182 Disallow: /xwiki/bin/inline/
183 Disallow: /xwiki/bin/lifeblog/
184 Disallow: /xwiki/bin/login/
185 Disallow: /xwiki/bin/loginerror/
186 Disallow: /xwiki/bin/logout/
187 Disallow: /xwiki/bin/objectremove/
188 Disallow: /xwiki/bin/pdf/
189 Disallow: /xwiki/bin/preview/
190 Disallow: /xwiki/bin/propadd/
191 Disallow: /xwiki/bin/propdelete/
192 Disallow: /xwiki/bin/propupdate/
193 Disallow: /xwiki/bin/register/
194 Disallow: /xwiki/bin/save/
195 Disallow: /xwiki/bin/skin/
196 Disallow: /xwiki/bin/status/
197 Disallow: /xwiki/bin/upload/
198 Disallow: /xwiki/bin/viewattachrev/
199 Disallow: /xwiki/bin/viewrev/
200 Disallow: /xwiki/bin/xmlrpc/
201 # It could be also usefull to block certain spaces from crawling,
202 # especially if this spaces doesn't provide new content
203 Disallow: /xwiki/bin/view/Main/
204 Disallow: /xwiki/bin/view/XWiki/
205 # on the other hand you would like to have your recent (public) changes included
206 Allow: /xwiki/bin/view/Main/Dashboard
207 {{/code}}
208
209
210 **Note:**
211
212 For Tomcat6 the placement of the ##robots.txt## file should be within the //$TOMCAT/webapps/ROOT// folder and should have permission 644 applied.
213
214 {{code}}
215 -rw-r--r-- 1 root www 1478 Jan 8 15:52 robots.txt
216 {{/code}}
217
218 In order to test if the ##robots.txt## file is either accessable or working as desired use this [[checker>>http://www.frobee.com/robots-txt-check]].
219
220 = Statistics =
221
222 {{info}}
223 This is no longer true starting with XE 1.4M2 since statistics are now put on a queue and written in a different thread in the database in one go, thus reducing the overhead to a maximum.
224 {{/info}}
225
226 The statistics module is off by default since it's quite database intensive. If you don't need it you should turn it off.
227
228 = Monitoring =
229
230 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 ##xwiki.cfg##:
231
232 {{code language="null"}}
233 xwiki.monitor=0
234 {{/code}}
235
236 = Cache sizes =
237
238 Tune the document cache in ##xwiki.cfg##. The value depends on how much memory you have. The higher the better. A good reasonable value is 1000.
239
240 {{code language="none"}}
241 xwiki.store.cache.capacity=1000
242 {{/code}}
243
244 = Cache Macro =
245
246 It's possible to perform selective content caching by using the [[Cache Macro>>extensions:Extension.Cache Macro]].
247
248 = Rendering cache =
249
250 Some pages are complex to render (they may aggregate outside data for example or do complex and slow queries). For theses pages you can use rendering cache.
251
252 == Configuration based ==
253
254 Pages can be cached (i.e. their rendered content cached) to speed up displaying. The configuration is done in ##xwiki.properties## with the following configuration options:
255
256 {{code language="none"}}
257 #-# [Since 2.4M1]
258 #-# Indicate if the rendering cache is enabled.
259 #-# Default value is false.
260 # core.renderingcache.enabled=true
261
262 #-# [Since 2.4M1]
263 #-# A list of Java regex patterns matching full documents reference.
264 # core.renderingcache.documents=wiki:Space\.Page
265 # core.renderingcache.documents=wiki:Space\..*
266
267 #-# [Since 2.4M1]
268 #-# The time (in seconds) after which data should be removed from the cache when not used.
269 #-# Default value is 300 (5 min).
270 # core.renderingcache.duration=300
271
272 #-# [Since 2.4M1]
273 #-# The size of the rendering cache. Not that it's not the number of cached documents but the number of cached results.
274 #-# (For a single document several cache entries are created, because each action, language and request query string
275 #-# produces a unique rendering result)
276 #-# Default value is 100.
277 # core.renderingcache.size=100
278 {{/code}}
279
280 You can force a page to refresh using ##refresh=1## in the URL.
281
282 Since 6.2 it's also possible to programmatically refresh any document cache using ##com.xpn.xwiki.internal.cache.rendering.RenderingCache## component:
283
284 {{code language="java"}}
285 @Inject
286 private RenderingCache renderingCache;
287
288 ...
289
290 renderingCache.flushWholeCache();
291 renderingCache.flushCache(new DocumentReference("xwiki", "MySpace", "MyCachedDocument"));
292 {{/code}}
293
294 == Enabled using velocity in document content itself (XWiki 1.0 syntax only) ==
295
296 You can add the following to their content to cache them after they are rendered. Note that the document is refreshed whenever the content of the document changes, and the cache takes into account the URL, so it is pretty safe to add a long cache duration for all documents that don't contain scripts gathering data from the wiki. For example to cache the rendered content for 60 seconds you would add:
297
298 {{code language="none"}}
299 $context.setCacheDuration(60)
300 {{/code}}
301
302 Since 1.5M2, you can set the default rendering cache duration for all pages in ##xwiki.cfg##:
303
304 {{code language="none"}}
305 ## cache all rendered documents for one hour
306 xwiki.rendering.defaultCacheDuration=3600
307 {{/code}}
308
309 Setting the default cache duration to a large value, and manually disabling the cache in dynamic pages would really speed up the wiki, since the rendering is one of the most time consuming processes.
310
311 = Merge the CSS files =
312
313 In order to reduce the number of requests and files that are downloaded from the browser or client, it could help to merge all XWiki CSS files into a single one. See the [[Merge CSS Script>>extensions:Extension.Merge CSS]].
314
315 = Set up NginX =
316
317 If you experience //__heavy loads__// on your wiki, you could try using NginX.
318
319 NginX is used to fetch static content: images, javascript, styles, etc, but it can also be used as a reverse-proxy to pass requests down to the web container (e.g. Tomcat on port 8080).
320
321 Unlike Apache, which instantiates a new process per every static file, NginX uses the same process to fetch all the static data, and thus gives you extra perfomance "for free".
322
323 For more info on setting up NginX check [[this guide>>NginX]].
324
325 = Backlinks =
326
327 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 ##xwiki.cfg##:
328
329 {{code language="none"}}
330 xwiki.backlinks=0
331 {{/code}}
332
333 = Versioning =
334
335 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 ##xwiki.cfg##:
336
337 {{code language="none"}}
338 xwiki.store.versioning=0
339 {{/code}}
340
341 = Custom Mapping =
342
343 In some cases you may not want to rely on XWiki's generic database schema for storing XClass data and instead you'd like to provide your own optimized table. For these use cases you can use [[Custom Mapping>>platform:DevGuide.CustomMapping]].
344
345 = Wiki syntax features for XWiki Syntax 1.0 =
346
347 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 ##xwiki-core-*.jar/META-INF/services/com.xpn.xwiki.render.*##. The wiki rendering is the most costly operation in the rendering process, so any disabled feature counts.

About

About

Support

Platform

User Guide

Admin Guide

Developer Guide

Projects

XWiki

Extensions

Other

Contribute

Status

Practices

Under the Hood

Get Involved

Get Connected