Wiki source code of Performance

Version 111.4 by Eduard Moraru on 2021/03/22

version	line-number	content
22.1	1	{{box cssClass="floatinginfobox" title="Contents"}}
	2	{{toc/}}
	3	{{/box}}
20.1	4
17.1	5	Here are some tips to increase XWiki's performance.
10.1	6
49.1	7	= Clustering =
	8
89.1	9	If you need high availability or if the load on your XWiki instance is too high you can [[configure XWiki in a cluster>>Documentation.AdminGuide.Clustering.WebHome]] to spread the load.
49.1	10
48.1	11	= Standalone Solr =
	12
110.2	13	By default XWiki use an embedded instance of Solr for ease of use, but if you struggle with very slow searches, you should try a external Solr instance.
	14	You can use ##debug=true## in the URL of the search to see how much time is spent inside Solr to verify if Solr is taking a long time, or the issue is somewhere else, for example the XWiki UI.
50.1	15
65.1	16	See [[Performance Guide in Solr module documentation>>extensions:Extension.Solr Search API#HPerformances]].
64.1	17
42.1	18	= Slow random number generation on UNIX =
	19
67.1	20	The library used for random number generation in Oracle's JVM relies on ##/dev/random## by default for UNIX platforms.
42.1	21
48.3	22	Although ##/dev/random## is more secure, it's possible to use ##/dev/urandom## if the default JVM configuration instead.
42.1	23
	24	To determine if your operating system exhibits this behavior, try displaying a portion of the file from a shell prompt:
	25
45.1	26	{{code language="bash"}}
42.1	27	head -n 1 /dev/random
45.1	28	{{/code}}
42.1	29
79.1	30	If the command returns immediately, you can use ##/dev/random## as the default generator for Oracle's JVM. If the command does not return immediately, use on of the following solutions to use ##/dev/urandom##:
42.1	31
79.1	32	== JVM setup ==
	33
44.1	34	1. Open the ##$JAVA_HOME/jre/lib/security/java.security## file in a text editor.
	35	1. Change the line:
50.1	36	{{code language="properties"}} securerandom.source=file:/dev/random{{/code}}
42.1	37	to read:
50.1	38	{{code language="properties"}} securerandom.source=file:/dev/urandom{{/code}}
44.1	39	1. Save your change and exit the text editor.
42.1	40
79.1	41	== Command line parameter ==
	42
109.1	43	The same effect can be obtained using ##-Djava.security.egd=file:/dev/./urandom## in the Java command line (usually in the application server configuration).
79.1	44
20.2	45	= Gzip compression and caching of static pages =
14.1	46
92.1	47	HTTP compression is a capability that can be built into web servers and web clients to improve transfer speed and bandwidth utilization. HTTP data is compressed before it is sent from the server: compliant browsers will announce what methods are supported to the server before downloading the correct format; browsers that do not support compliant compression method will download uncompressed data.
14.1	48
94.1	49	Many application servers (Tomcat, etc.) and HTTP proxies (Apache HTTPd, Nginx, etc.) support it.
92.1	50
93.1	51	== In Apache HTTP Server ==
92.1	52
	53	The recommended solution is to set up an Apache Web Server in front of your servlet container and install/configure the following modules:
	54
20.1	55	* [[mod-deflate>>http://httpd.apache.org/docs/2.0/mod/mod_deflate.html]]
81.1	56	* [[mod-expires>>http://httpd.apache.org/docs/2.0/mod/mod_expires.html]]
20.1	57	* [[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)
	58
14.1	59	Modify your Apache configuration file to load the different modules:
	60
20.1	61	{{code language="none"}}
14.1	62	LoadModule expires_module /usr/lib/apache2/modules/mod_expires.so
	63	LoadModule deflate_module /usr/lib/apache2/modules/mod_deflate.so
	64	LoadModule proxy_module /usr/lib/apache2/modules/mod_proxy.so
	65	# Depends: proxy
	66	LoadModule proxy_ajp_module /usr/lib/apache2/modules/mod_proxy_ajp.so
20.1	67	{{/code}}
14.1	68
37.1	69	//Alternatively you can run the following commands as root (sudo)//
	70
	71	{{code language="bash"}}
	72	a2enmod deflate
	73	a2enmod proxy_ajp
	74	a2enmod expires
	75	{{/code}}
	76
32.2	77	and configure your different modules as described below:
14.1	78
92.1	79	=== Mod Deflate Configuration ===
14.1	80
20.1	81	{{code language="none"}}
14.1	82	vwwwpro-1:~# cat /etc/apache2/conf.d/deflate
111.3	83	<Location />
14.1	84	# Insert filter
	85	SetOutputFilter DEFLATE
	86
	87	# Netscape 4.x has some problems...
	88	BrowserMatch ^Mozilla/4 gzip-only-text/html
	89
	90	# Netscape 4.06-4.08 have some more problems
20.1	91	BrowserMatch ^Mozilla/4.0[678] no-gzip
14.1	92
	93	# MSIE masquerades as Netscape, but it is fine
20.1	94	# BrowserMatch bMSIE !no-gzip !gzip-only-text/html
14.1	95
	96	# NOTE: Due to a bug in mod_setenvif up to Apache 2.0.48
	97	# the above regex won't work. You can use the following
	98	# workaround to get the desired effect:
20.1	99	BrowserMatch bMSI[E] !no-gzip !gzip-only-text/html
14.1	100
	101	# Don't compress images
20.1	102	SetEnvIfNoCase Request_URI .(?:gif\|jpe?g\|png)$ no-gzip dont-vary
14.1	103
	104	# Make sure proxies don't deliver the wrong content
	105	#Header append Vary User-Agent env=!dont-vary
	106	</Location>
20.1	107	{{/code}}
14.1	108
37.1	109	//On debian apache2 the config file for deflate is located under /etc/apache2/mods-enabled/deflate.conf//
	110
92.1	111	=== Mod Expire Configuration ===
14.1	112
20.1	113	{{code language="none"}}
14.1	114	vwwwpro-1:~# cat /etc/apache2/conf.d/expires
111.3	115	<Location /xwiki/skins/>
14.1	116	ExpiresActive on
	117	ExpiresDefault "access plus 1 day"
	118	</Location>
	119
111.3	120	<Location /xwiki/bin/skin/>
14.1	121	ExpiresActive on
	122	ExpiresDefault "access plus 1 day"
	123	</Location>
20.1	124	{{/code}}
14.1	125
92.1	126	=== Mod Proxy AJP Configuration ===
14.1	127
20.1	128	{{code language="none"}}
	129	ProxyRequests Off
14.1	130	<Proxy *>
	131	Order deny,allow
	132	Allow from all
	133	</Proxy>
	134	ProxyPreserveHost On
	135	ProxyPass /xwiki ajp://192.168.1.181:8009/xwiki
20.1	136	{{/code}}
14.1	137
20.1	138	where ##ajp:~/~/192.168.1.181:8009/xwiki## is the internal address of your Servlet container where XWiki is running.
14.1	139
37.1	140	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.//
	141
	142	{{code}}
	143	<!-- disable to use ajp connector instead
	144	<Connector port="8080" protocol="HTTP/1.1"
	145	connectionTimeout="20000"
	146	URIEncoding="UTF-8"
111.3	147	redirectPort="8443" />
37.1	148	-->
	149	{{/code}}
	150
39.1	151	Uncomment the following line by removing the {{code}}<!-- -->{{/code}} and add {{code}}URIEncoding="UTF-8"{{/code}} to it.Maybe give a comment too.
37.1	152
	153	{{code}}
	154	<!-- Activate ajp connector for apache proxy_ajp -->
111.3	155	<Connector port="8009" protocol="AJP/1.3" redirectPort="8443" URIEncoding="UTF-8"/>
37.1	156	{{/code}}
	157
20.2	158	= Memory =
9.1	159
34.1	160	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:
36.1	161
78.1	162	* For Java 8 (i.e. XWiki >= 8.1). Notice that there's no permgen anymore in Java 8:
96.1	163	** Small and medium installs: A minimum of 1024MB (##-Xmx1024m)##
	164	** Large installs: 2048MB or beyond (##-Xmx2048m).##
78.1	165	* For Java 7 (i.e. XWiki < 8.1)
	166	** Small installs: A minimum of 512MB of heap memory and 196MB of permGen (##-Xmx512m -XX:MaxPermSize=196m##)
	167	** Medium installs: 1024MB for the heap and 196MB of permGen (##-Xmx1024m -XX:MaxPermSize=196m##)
	168	** Large installs: 2048MB (or beyond) for the heap and 196MB of permGen (##-Xmx2048m -XX:MaxPermSize=196m##).
9.1	169
53.3	170	{{info}}
53.1	171	You should not increase the memory beyond what you need because increasing it means that there's more Objects in memory at any time and the automatic JVM Garbage Collector has to work harder to clean itself, which can results in performance degradation in XWiki (since a full GC will pause the application for a longer time).
53.3	172	{{/info}}
53.1	173
34.1	174	{{warning}}
88.4	175	Note that storing attachments with the default (in database) storage mechanism is very memory intensive. See the [[administrators guide to attachments>>Documentation.AdminGuide.Attachments]] for more information about memory cost and the alternative filesystem based attachment store.
38.2	176
82.1	177	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. To track the progress on this issue, please see [[XWIKI-10594>>https://jira.xwiki.org/browse/XWIKI-10594]].
34.1	178	{{/warning}}
20.1	179
76.1	180	{{warning}}
88.5	181	If you use HSQLDB as the wiki database, be aware that the full content of the database is stored in memory and thus the memory requirements are higher. See [[HSQLDB installation page>>Documentation.AdminGuide.Installation.InstallationWAR.InstallationHSQL.WebHome]] for more details.
76.1	182	{{/warning}}
	183
35.1	184	For your information here are the values used for the xwiki.org site:
	185
	186	{{code}}
106.3	187	CATALINA_OPTS="-server -Xms800m -Xmx1600m -Dfile.encoding=utf-8 -Djava.awt.headless=true -XX:+UseParallelGC -XX:MaxGCPauseMillis=100"
35.1	188	{{/code}}
	189
105.1	190	= Sizing =
	191
105.2	192	To give you an idea about what you need to run XWiki on, [[XWiki SAS>>https://xwiki.com]] has the following configuration for its cloud instances:
105.1	193
106.4	194	* 2GB of RAM (See [[XWiki memory needs>>#HMemory]]),
106.1	195	* 2 cores(((
	196	{{code language="none"}}
	197	AMD Opteron(tm) Processor 6386 SE
	198	cpu MHz : 2800.000
	199	cache size : 2048 KB
106.2	200	{{/code}}
106.1	201	)))
105.1	202	* 16GB disk size by default
	203
20.2	204	= Database Indexes =
1.1	205
90.1	206	Make sure you've set [[Database indexes>>Documentation.AdminGuide.Performances.Database Administration.WebHome]]. This is especially important when you start having lots of documents.
1.1	207
74.1	208	= Large number of users =
	209
	210	When you have large number of users it's recommended to turn on implicit All Group, i.e. to consider that all users are members of XWiki.XWikiAllGroup by default in the configuration. This is achieved by editing the ##xwiki.cfg## file and setting:
	211
	212	{{code language="none"}}
	213	xwiki.authentication.group.allgroupimplicit=1
	214	{{/code}}
	215
75.1	216	Then you should remove all the XObjects from the XWikiAllGroup page but you should keep the page since otherwise you won't be able to set permissions for this group. This will prevent XWiki from having to load all that page's XObjects representing the users (thousands of them if you have thousands of users).
74.1	217
75.2	218	Also make sure that the ##XWikiAllGroup## is listed in the ##xwiki.users.initialGroups## property (it's there by default if you haven't touched that property):
	219
	220	{{code language="none"}}
	221	#-# List of groups that a new user should be added to by default after registering. Comma-separated list of group
	222	#-# document names.
	223	# xwiki.users.initialGroups=XWiki.XWikiAllGroup
	224	{{/code}}
	225
20.2	226	= Robots.txt =
15.1	227
86.6	228	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 and put it in your webserver configuration.
15.1	229
85.1	230	Some example:
	231
20.1	232	{{code language="none"}}
15.1	233	User-agent: *
86.7	234	# Prevent bots from executing all actions except "view" since:
86.1	235	# 1) we don't want bots to execute stuff in the wiki!
86.2	236	# 2) we don't want bots to consume CPU and memory
86.7	237	# (for example to perform exports)
	238	# Note: You may want to allow /download/ if you wish to have
	239	# attachments indexed.
111.1	240	# Note2: Using * instead of /bin/ to also match path-based
	241	# subwikis like "/xwiki/wiki/wikialias/view/Space/Page"
	242	Disallow: /xwiki/*/viewattachrev/
	243	Disallow: /xwiki/*/viewrev/
	244	Disallow: /xwiki/*/pdf/
	245	Disallow: /xwiki/*/tex/
	246	Disallow: /xwiki/*/edit/
	247	Disallow: /xwiki/*/create/
	248	Disallow: /xwiki/*/inline/
	249	Disallow: /xwiki/*/preview/
	250	Disallow: /xwiki/*/save/
	251	Disallow: /xwiki/*/saveandcontinue/
	252	Disallow: /xwiki/*/rollback/
	253	Disallow: /xwiki/*/deleteversions/
	254	Disallow: /xwiki/*/cancel/
	255	Disallow: /xwiki/*/delete/
	256	Disallow: /xwiki/*/deletespace/
	257	Disallow: /xwiki/*/undelete/
	258	Disallow: /xwiki/*/reset/
	259	Disallow: /xwiki/*/register/
	260	Disallow: /xwiki/*/propupdate/
	261	Disallow: /xwiki/*/propadd/
	262	Disallow: /xwiki/*/propdisable/
	263	Disallow: /xwiki/*/propenable/
	264	Disallow: /xwiki/*/propdelete/
	265	Disallow: /xwiki/*/objectadd/
	266	Disallow: /xwiki/*/commentadd/
	267	Disallow: /xwiki/*/commentsave/
	268	Disallow: /xwiki/*/objectsync/
	269	Disallow: /xwiki/*/objectremove/
	270	Disallow: /xwiki/*/attach/
	271	Disallow: /xwiki/*/upload/
	272	Disallow: /xwiki/*/download/
	273	Disallow: /xwiki/*/temp/
	274	Disallow: /xwiki/*/downloadrev/
	275	Disallow: /xwiki/*/dot/
	276	Disallow: /xwiki/*/svg/
	277	Disallow: /xwiki/*/delattachment/
	278	Disallow: /xwiki/*/skin/
	279	Disallow: /xwiki/*/jsx/
	280	Disallow: /xwiki/*/ssx/
	281	Disallow: /xwiki/*/login/
	282	Disallow: /xwiki/*/loginsubmit/
	283	Disallow: /xwiki/*/loginerror/
	284	Disallow: /xwiki/*/logout/
	285	Disallow: /xwiki/*/charting/
	286	Disallow: /xwiki/*/lock/
	287	Disallow: /xwiki/*/redirect/
	288	Disallow: /xwiki/*/admin/
	289	Disallow: /xwiki/*/export/
	290	Disallow: /xwiki/*/import/
	291	Disallow: /xwiki/*/get/
	292	Disallow: /xwiki/*/distribution/
	293	Disallow: /xwiki/*/imagecaptcha/
	294	Disallow: /xwiki/*/unknown/
111.4	295	# Note: In addition, this matches both old /xwiki/bin/webjars/
	296	# and new /xwiki/webjars paths.
111.1	297	Disallow: /xwiki/*/webjars/
111.4	298	# Don't index additional UI-related resources.
	299	Disallow: /xwiki/resources/
86.2	300	# Don't index sandbox content since it's sample content
111.1	301	Disallow: /xwiki/*/view/Sandbox/
86.2	302	# Don't index Admin space since it contains Admin stuff.
	303	# Note that the Admin space is protected by permissions
	304	# anyway but this acts as a safety net to not have private
	305	# info leaked on the internet ;)
111.1	306	Disallow: /xwiki/*/view/Admin/
86.2	307	# Don't index Stats data (just because it's not useful and
	308	# those pages are a bit CPU intensive)
111.1	309	Disallow: /xwiki/*/view/Stats/
86.2	310	# Don't index Panels data (because we don't want it
	311	# indexed on the internet)
111.1	312	Disallow: /xwiki/*/view/Panels/
	313	# Don't index the search page.
	314	Disallow: /xwiki/*/Main/Search
	315	# Don't index the REST API.
	316	Disallow: /xwiki/rest/
	317	# These are just UI elements which can cause infinite loops in
	318	# web crawlers. See https://jira.xwiki.org/browse/XWIKI-16915
	319	Disallow: /xwiki/?xpage=*
86.1	320	{{/code}}
	321
	322	Other example:
	323
	324	{{code}}
	325	[...]
85.1	326	# It could be also useful to block certain spaces from crawling,
22.1	327	# especially if this spaces doesn't provide new content
	328	Disallow: /xwiki/bin/view/Main/
	329	Disallow: /xwiki/bin/view/XWiki/
85.1	330	# On the other hand you would like to have your recent (public) changes included
22.1	331	Allow: /xwiki/bin/view/Main/Dashboard
20.1	332	{{/code}}
15.1	333
32.2	334	Note:
32.1	335
32.2	336	For Tomcat6 the placement of the ##robots.txt## file should be within the //$TOMCAT/webapps/ROOT// folder and should have permission 644 applied.
32.1	337
	338	{{code}}
	339	-rw-r--r-- 1 root www 1478 Jan 8 15:52 robots.txt
	340	{{/code}}
	341
32.2	342	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]].
32.1	343
20.2	344	= Statistics =
1.1	345
20.1	346	{{info}}
	347	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.
	348	{{/info}}
15.1	349
32.2	350	The statistics module is off by default since it's quite database intensive. If you don't need it you should turn it off.
110.4	351	The current recommendation is to use the [[Matomo extension>>extensions:Extension.Piwiki Integration]] for statistics instead.
1.2	352
52.3	353	= Document Cache =
1.2	354
52.3	355	You can tune the Document cache in the ##xwiki.cfg## configuration file. The value depends on how much memory you have. The higher the better. A good reasonable value is 1000.
2.1	356
20.1	357	{{code language="none"}}
19.1	358	xwiki.store.cache.capacity=1000
20.1	359	{{/code}}
8.1	360
25.1	361	= Cache Macro =
	362
26.1	363	It's possible to perform selective content caching by using the [[Cache Macro>>extensions:Extension.Cache Macro]].
25.1	364
77.1	365	= LESS CSS Performances =
51.1	366
77.1	367	[[LESS>>extensions:Extension.LESS Module]] is a preprocessor used to generate CSS files for skins and skin extensions. See the [[Performances section>>extensions:Extension.LESS Module#HPerformances]] of the LESS module documentation to learn more about how to optimize its cache for performances, and to set the appropriate number of simultaneous compilations your server can handle.
51.1	368
20.2	369	= Rendering cache =
2.1	370
30.1	371	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.
	372
29.1	373	== Configuration based ==
25.1	374
32.2	375	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:
25.1	376
	377	{{code language="none"}}
	378	#-# [Since 2.4M1]
	379	#-# Indicate if the rendering cache is enabled.
	380	#-# Default value is false.
	381	# core.renderingcache.enabled=true
	382
	383	#-# [Since 2.4M1]
	384	#-# A list of Java regex patterns matching full documents reference.
	385	# core.renderingcache.documents=wiki:Space\.Page
	386	# core.renderingcache.documents=wiki:Space\..*
	387
	388	#-# [Since 2.4M1]
	389	#-# The time (in seconds) after which data should be removed from the cache when not used.
	390	#-# Default value is 300 (5 min).
	391	# core.renderingcache.duration=300
	392
	393	#-# [Since 2.4M1]
	394	#-# The size of the rendering cache. Not that it's not the number of cached documents but the number of cached results.
	395	#-# (For a single document several cache entries are created, because each action, language and request query string
	396	#-# produces a unique rendering result)
	397	#-# Default value is 100.
	398	# core.renderingcache.size=100
	399	{{/code}}
	400
31.1	401	You can force a page to refresh using ##refresh=1## in the URL.
30.1	402
41.1	403	Since 6.2 it's also possible to programmatically refresh any document cache using ##com.xpn.xwiki.internal.cache.rendering.RenderingCache## component:
39.1	404
	405	{{code language="java"}}
	406	@Inject
	407	private RenderingCache renderingCache;
	408
	409	...
	410
	411	renderingCache.flushWholeCache();
	412	renderingCache.flushCache(new DocumentReference("xwiki", "MySpace", "MyCachedDocument"));
	413	{{/code}}
	414
25.1	415
20.2	416	= Merge the CSS files =
11.1	417
110.5	418	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>>snippets:Extension.Merge CSS]].
11.1	419
20.2	420	= Set up NginX =
19.2	421
32.2	422	If you experience //__heavy loads__// on your wiki, you could try using NginX.
19.3	423
36.1	424	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).
19.2	425
32.2	426	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".
19.2	427
91.1	428	For more info on setting up NginX check [[this guide>>Documentation.AdminGuide.Installation.NginX.WebHome]].
19.2	429
107.1	430	= Local resource access =
	431
108.1	432	[[See URL API>>extensions:Extension.URL API#HResourcemodificationdate]].
107.1	433
20.2	434	= Backlinks =
4.1	435
20.1	436	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##:
	437
	438	{{code language="none"}}
19.1	439	xwiki.backlinks=0
20.1	440	{{/code}}
5.1	441
20.2	442	= Versioning =
5.1	443
32.2	444	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##:
20.1	445
	446	{{code language="none"}}
19.1	447	xwiki.store.versioning=0
20.1	448	{{/code}}
6.1	449
21.1	450	= Custom Mapping =
6.1	451
32.2	452	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]].
21.1	453
73.1	454	= LDAP =
	455
	456	== Disable LDAP sub groups search ==
	457
	458	By default when loading a LDAP group, each member is searched and loaded to figure out if it's a group or not (and then load the sub group members, etc). Since 7.2 If you know there is not sub group in your LDAP groups you can disable it and speed up quite a lot big groups handling using ##xwiki.authentication.ldap.group_sync_resolve_subgroups## property in ##xwiki.cfg## configuration file.
	459
56.1	460	= Performance tree =
	461
57.1	462	Since 7.1 it's possible to directly get a tree of time spent in each step of the request by using [[debug mode>>dev:Community.Debugging#HDebugmode]].
68.1	463
98.2	464	= Navigation Tree =
98.1	465
	466	The Navigation Panel and other navigation trees can have some small performance issues under very high volumes. Here ares some base measures we did on some developer laptops to give you some ideas of the performance you should expect:
	467
	468	Measure set 1:
	469
111.1	470	(% class="table-bordered" style="width:100%" %)
101.2	471	\|=(% width="20%" %)DB\|=(% width="10%" %)Levels\|=(% width="10%" %)Spaces\|=(% width="10%" %)Pages\|=(% width="15%" %)Requests\|=Time
100.1	472	\|MySQL\|5\|6887\|4049\|31\|180ms
	473	\|HSQLDB\|5\|6762\|4063\|27\|138ms
	474	\|MySQL\|1\|2514\|4962\|27\|331ms
	475	\|HSQLDB\|1\|2377\|4718\|21\|3.15s
98.1	476
	477	Measure set 2:
	478
111.1	479	(% class="table-bordered" style="width:100%" %)
101.2	480	\|=(% width="20%" %)DB\|=(% width="10%" %)Levels\|=(% width="10%" %)Spaces\|=(% width="10%" %)Pages\|=(% width="15%" %)Requests\|=Time
100.1	481	\|Oracle\|5\|6943\|4106\|20\|119ms
	482	\|Oracle\|1\|2493\|4982\|20\|153ms
98.1	483
	484	Measure set 3:
	485
111.1	486	(% class="table-bordered" style="width:100%" %)
101.2	487	\|=(% width="20%" %)DB\|=(% width="10%" %)Levels\|=(% width="10%" %)Spaces\|=(% width="10%" %)Pages\|=(% width="15%" %)Requests\|=Time
101.1	488	\|Oracle\|1\|2485\|4991\|20\|151ms
	489	\|PostgreSQL\|1\|2494\|4991\|20\|125ms
98.1	490
103.1	491	Measure set 4 (XWiki 10.5, Intel i7 CPU, SSD Storage):
102.1	492
111.1	493	(% class="table-bordered" style="width:100%" %)
102.1	494	\|=(% width="20%" %)DB\|=(% width="10%" %)Levels\|=(% width="10%" %)Spaces\|=(% width="10%" %)Pages\|=(% width="15%" %)Requests\|=Time
104.1	495	\|PostgreSQL 10\|5\|6847\|4052\|25\|74ms
102.1	496
68.1	497	= Legacy =
	498
71.1	499	== Monitor plugin ==
70.1	500
	501	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##:
	502
	503	{{code language="properties"}}
	504	xwiki.monitor=0
	505	{{/code}}
	506
68.1	507	== 1.0 rendering cache using velocity in document content itself ==
	508
	509	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:
	510
	511	{{code language="none"}}
	512	$context.setCacheDuration(60)
	513	{{/code}}
	514
	515	Since 1.5M2, you can set the default rendering cache duration for all pages in ##xwiki.cfg##:
	516
	517	{{code language="none"}}
	518	## cache all rendered documents for one hour
	519	xwiki.rendering.defaultCacheDuration=3600
	520	{{/code}}
	521
	522	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.
69.1	523
72.1	524	== Wiki syntax features for XWiki Syntax 1.0 ==
69.1	525
	526	If you're using XWiki Syntax 1.0 and if you don't plan to use all of the markup 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.
	527
	528	Now this will have no effect if you're using another syntax, like XWiki Syntax 2.x.

Wiki source code of Performance

Quick Links

Navigation

About

About

Support

Platform

User Guide

Admin Guide

Developer Guide

Projects

XWiki

Extensions

Other

Contribute

Status

Practices

Under the Hood

Get Involved

Get Connected