Changes for page Performance

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.kayasaman
	1	+XWiki.ManuelSmeria

Content

...	...	@@ -22,7 +22,7 @@
22	22	LoadModule proxy_ajp_module /usr/lib/apache2/modules/mod_proxy_ajp.so
23	23	{{/code}}
24	24
25		-And configure your different modules as described below.
	25	+and configure your different modules as described below:
26	26
27	27	== Mod Deflate Configuration ==
28	28
...	...	@@ -85,7 +85,7 @@
85	85
86	86	= Memory =
87	87
88		-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. A good default value is 384MB (-Xmx384m).
	88	+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. A good default value is 384MB (-Xmx384m).
89	89
90	90	Here are the values used for xwiki.org's web site:
91	91
...	...	@@ -95,15 +95,15 @@
95	95
96	96	= Database Indexes =
97	97
98		-Make sure you've set [[Database indexes>>Database Administration||target=""]]. This is especially important when you start having lots of documents.
	98	+Make sure you've set [[Database indexes>>Database Administration]]. This is especially important when you start having lots of documents.
99	99
100	100	= Panels =
101	101
102		-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).
	102	+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).
103	103
104	104	= Robots.txt =
105	105
106		-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 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:
	106	+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:
107	107
108	108	{{code language="none"}}
109	109	User-agent: *
...	...	@@ -146,19 +146,16 @@
146	146	{{/code}}
147	147
148	148
149		-**Note**
	149	+**Note:**
150	150
151		-For Tomcat6 the placement of the robots.txt file should be within the $TOMCAT/webapps/ROOT folder and should have permission 644 applied.
	151	+For Tomcat6 the placement of the ##robots.txt## file should be within the //$TOMCAT/webapps/ROOT// folder and should have permission 644 applied.
152	152
153	153	{{code}}
154	154	-rw-r--r-- 1 root www 1478 Jan 8 15:52 robots.txt
155	155	{{/code}}
156	156
	157	+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]].
157	157
158		-In order to test if the robots.txt file is either accessable or working as desired this link is useful:
159		-
160		-[[Robots Check>>http://http://www.frobee.com/robots-txt-check]]
161		-
162	162	= Statistics =
163	163
164	164	{{info}}
...	...	@@ -165,7 +165,7 @@
165	165	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.
166	166	{{/info}}
167	167
168		-The statistics module is off by default since it's quite Database intensive. If you don't need it you should turn it off.
	165	+The statistics module is off by default since it's quite database intensive. If you don't need it you should turn it off.
169	169
170	170	= Monitoring =
171	171
...	...	@@ -193,7 +193,7 @@
193	193
194	194	== Configuration based ==
195	195
196		-Pages can be cached (ie their rendered content cached) to speed up displaying. The configuration is done in ##xwiki.properties## with the following configuration options:
	193	+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:
197	197
198	198	{{code language="none"}}
199	199	#-# [Since 2.4M1]
...	...	@@ -240,17 +240,17 @@
240	240
241	241	= Merge the CSS files =
242	242
243		-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 Snippet>>extensions:Extension.Merge CSS]]
	240	+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]].
244	244
245	245	= Set up NginX =
246	246
247		-If you experience //__heavy loads__// on your wiki, you could try using //NginX//.
	244	+If you experience //__heavy loads__// on your wiki, you could try using NginX.
248	248
249		-//NginX// is used to fetch //static// content: //images, javascript, styles, etc.//
	246	+NginX is used to fetch static content: images, javascript, styles, etc.
250	250
251		-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"//.
	248	+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".
252	252
253		-For more info on setting up //NginX// look [[here>>NginX]]
	250	+For more info on setting up NginX check [[this guide>>NginX]].
254	254
255	255	= Backlinks =
256	256
...	...	@@ -262,7 +262,7 @@
262	262
263	263	= Versioning =
264	264
265		-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##
	262	+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##:
266	266
267	267	{{code language="none"}}
268	268	xwiki.store.versioning=0
...	...	@@ -270,7 +270,7 @@
270	270
271	271	= Custom Mapping =
272	272
273		-In some cases you may want not 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]].
	270	+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]].
274	274
275	275	= Wiki syntax features for XWiki Syntax 1.0 =
276	276