Performance recommendations - Revision history

Epoe: the linked metaskills.net page now has a different URL. The new URL is found in the metaskills.net archive - http://metaskills.net/archive.html

2012-12-28T15:44:36Z

the linked metaskills.net page now has a different URL. The new URL is found in the metaskills.net archive - http://metaskills.net/archive.html

← Older revision		Revision as of 15:44, 28 December 2012
Line 120:		Line 120:
	</ifmodule>		</ifmodule>

	More info: [http://~~www.~~metaskills.net/~~blog~~/~~heuristics~~/~~sysadmin~~/how-to-control-browser-caching-with-apache-2 www.metaskills.net]		More info: [http://metaskills.net/2006/02/19/how-to-control-browser-caching-with-apache-2/ www.metaskills.net]

	===IIS performance===		===IIS performance===

Tsala: /* See also */ subsection renaming as suggested in http://moodle.org/mod/forum/discuss.php?d=199101

2012-05-22T17:57:40Z

See also: subsection renaming as suggested in http://moodle.org/mod/forum/discuss.php?d=199101

← Older revision		Revision as of 17:57, 22 May 2012
Line 19:		Line 19:
	It is possible to load-balance a Moodle installation, for example by using more than one webserver. The separate webservers should query the same database and refer to the same filestore area, but otherwise the separation of the application layers is complete enough to make this kind of clustering feasible. Similarly, the database could be a cluster of servers (e.g. a MySQL cluster), but this is not an easy task and you should seek expert support, e.g. from a Moodle Partner.		It is possible to load-balance a Moodle installation, for example by using more than one webserver. The separate webservers should query the same database and refer to the same filestore area, but otherwise the separation of the application layers is complete enough to make this kind of clustering feasible. Similarly, the database could be a cluster of servers (e.g. a MySQL cluster), but this is not an easy task and you should seek expert support, e.g. from a Moodle Partner.

	===~~See also~~===		===Server cluster===

	Using Moodle forum discussions:		Using Moodle forum discussions:

Tsala: removing server cluster link and broken interlang link

2012-04-09T12:46:27Z

removing server cluster link and broken interlang link

← Older revision		Revision as of 12:46, 9 April 2012
Line 19:		Line 19:
	It is possible to load-balance a Moodle installation, for example by using more than one webserver. The separate webservers should query the same database and refer to the same filestore area, but otherwise the separation of the application layers is complete enough to make this kind of clustering feasible. Similarly, the database could be a cluster of servers (e.g. a MySQL cluster), but this is not an easy task and you should seek expert support, e.g. from a Moodle Partner.		It is possible to load-balance a Moodle installation, for example by using more than one webserver. The separate webservers should query the same database and refer to the same filestore area, but otherwise the separation of the application layers is complete enough to make this kind of clustering feasible. Similarly, the database could be a cluster of servers (e.g. a MySQL cluster), but this is not an easy task and you should seek expert support, e.g. from a Moodle Partner.

	~~'''~~See also~~'''~~:		===See also===
	*[[Server cluster]]
	*[http://moodle.org/mod/forum/discuss.php?d=~~4801 Scalability~~] ~~forum discussion.~~		Using Moodle forum discussions:
	*[http://moodle.org/mod/forum/discuss.php?d=~~57202 Moodle clustering~~] ~~forum discussion.~~
	*[http://moodle.org/mod/forum/discuss.php?d=~~44470 Software~~ load balancing] ~~forum discussion.~~		*[http://moodle.org/mod/forum/discuss.php?d=57202 Moodle clustering]
	*[http://moodle.org/mod/forum/discuss.php?d=~~49986 TCP load balancing~~] ~~forum dicsussion.~~		*[http://moodle.org/mod/forum/discuss.php?d=44470 Software load balancing]
			*[http://moodle.org/mod/forum/discuss.php?d=49986 TCP load balancing]
			*[http://moodle.org/mod/forum/discuss.php?d=88214 Installation for 3000 simultaneous users]

	==Hardware configuration==		==Hardware configuration==
Line 262:		Line 264:
	[[fr:Performance]]		[[fr:Performance]]
	[[ja:パフォーマンス]]		[[ja:パフォーマンス]]
	~~[[pl:Wydajnosc]]~~

Howardsmiller: /* Hardware configuration */

2011-11-29T11:06:34Z

Hardware configuration

← Older revision		Revision as of 11:06, 29 November 2011
Line 27:		Line 27:

	==Hardware configuration==		==Hardware configuration==
	'''Note''': The fastest and most effective change that you can make to improve performance is to '''increase the amount of RAM on your web server''' - get as much as possible (eg 4GB). Increasing primary memory will reduce the need for processes to swap to disk and will enable your server to handle more users.		'''Note''': The fastest and most effective change that you can make to improve performance is to '''increase the amount of RAM on your web server''' - get as much as possible (e.g. 4GB or more). Increasing primary memory will reduce the need for processes to swap to disk and will enable your server to handle more users.
	* Better performance is gained by obtaining the best '''processor capability''' you can, i.e. dual or dual core processors. A modern BIOS should allow you to enable hyperthreading, but check if this makes a difference to the overall performance of the processors by using a [http://en.wikipedia.org/wiki/Super_PI CPU benchmarking tool].		* Better performance is gained by obtaining the best '''processor capability''' you can, i.e. dual or dual core processors. A modern BIOS should allow you to enable hyperthreading, but check if this makes a difference to the overall performance of the processors by using a [http://en.wikipedia.org/wiki/Super_PI CPU benchmarking tool].
	* If you can afford them, use '''SCSI hard disks''' instead of SATA drives. SATA drives will increase your system's CPU utilization, whereas SCSI drives have their own integrated processors and come into their own when you have multiple drives. If you must have SATA drives, check that your motherboard and the drives themselves support NCQ (Native Command Queuing).		* If you can afford them, use '''SCSI hard disks''' instead of SATA drives. SATA drives will increase your system's CPU utilization, whereas SCSI drives have their own integrated processors and come into their own when you have multiple drives. If you must have SATA drives, check that your motherboard and the drives themselves support NCQ (Native Command Queuing).

Howardsmiller: /* Apache performance */

2011-11-29T10:34:53Z

Apache performance

← Older revision		Revision as of 10:34, 29 November 2011
Line 73:		Line 73:
	* Set the '''MaxClients''' directive correctly. Use this formula to help (which uses 80% of available memory to leave room for spare):		* Set the '''MaxClients''' directive correctly. Use this formula to help (which uses 80% of available memory to leave room for spare):
	MaxClients = Total available memory * 80% / Max memory usage of apache process		MaxClients = Total available memory * 80% / Max memory usage of apache process
	:Memory usage of apache process is usually 10MB but Moodle can easily use up to 100MB per process, so a general rule of thumb is to divide your available memory in megabytes by 10 to get ~~the value of~~ MaxClients. You are quite likely to find yourself lowering the MaxClients from its default of 150 on a Moodle server. To ~~find the max memory usage of apache processes~~ read the value from the shell command:		:Memory usage of apache process is usually 10MB but Moodle can easily use up to 100MB per process, so a general rule of thumb is to divide your available memory in megabytes by 100 to get a conservative setting for MaxClients. You are quite likely to find yourself lowering the MaxClients from its default of 150 on a Moodle server. To get a more accurate estimate read the value from the shell command:
	#ps -ylC httpd --sort:rss		#ps -ylC httpd --sort:rss

Howardsmiller: /* Apache performance */

2011-11-29T10:33:30Z

Apache performance

← Older revision		Revision as of 10:33, 29 November 2011
Line 73:		Line 73:
	* Set the '''MaxClients''' directive correctly. Use this formula to help (which uses 80% of available memory to leave room for spare):		* Set the '''MaxClients''' directive correctly. Use this formula to help (which uses 80% of available memory to leave room for spare):
	MaxClients = Total available memory * 80% / Max memory usage of apache process		MaxClients = Total available memory * 80% / Max memory usage of apache process
	:Memory usage of apache process is usually 10MB, so a general rule of thumb is to divide your available memory in megabytes by 10 to get the value of MaxClients. To find the max memory usage of apache processes read the value from the shell command:		:Memory usage of apache process is usually 10MB but Moodle can easily use up to 100MB per process, so a general rule of thumb is to divide your available memory in megabytes by 10 to get the value of MaxClients. You are quite likely to find yourself lowering the MaxClients from its default of 150 on a Moodle server. To find the max memory usage of apache processes read the value from the shell command:
	#ps -ylC httpd --sort:rss		#ps -ylC httpd --sort:rss

Libertymoodle: /* PHP performance - WinCache */

2011-10-21T08:55:21Z

PHP performance - WinCache

← Older revision		Revision as of 08:55, 21 October 2011
Line 55:		Line 55:

	===PHP performance===		===PHP performance===
	* You are strongly recommended to use a '''PHP accelerator''' to ease CPU load, such as [http://pecl.php.net/apc APC], [http://www.php-accelerator.co.uk/ PHPA], [http://trac.lighttpd.net/xcache/ Xcache] or [http://eaccelerator.net/ eAccelerator]. (Take care to choose a PHP accelerator that is known to work well with your version of PHP and note that Turck MMCache is [http://turckmmcache.exeprod.com/TheManifestoEnglish no longer maintained] and can cause failures with PHP 5).		* You are strongly recommended to use a '''PHP accelerator''' to ease CPU load, such as [http://pecl.php.net/apc APC], [http://www.php-accelerator.co.uk/ PHPA], [http://trac.lighttpd.net/xcache/ Xcache], [http://sourceforge.net/projects/wincache WinCache] or [http://eaccelerator.net/ eAccelerator]. (Take care to choose a PHP accelerator that is known to work well with your version of PHP and note that Turck MMCache is [http://turckmmcache.exeprod.com/TheManifestoEnglish no longer maintained] and can cause failures with PHP 5).
	* Improvements in read/write performance can be improved by putting the cached PHP pages on a [[TMPFS]] filesystem - but remember that you'll lose the cache contents when there is a power failure or the server is rebooted.		* Improvements in read/write performance can be improved by putting the cached PHP pages on a [[TMPFS]] filesystem - but remember that you'll lose the cache contents when there is a power failure or the server is rebooted.
	* Performance of PHP is better when installed as an '''Apache/IIS ISAPI module''' (rather than a CGI).		* Performance of PHP is better when installed as an '''Apache/IIS ISAPI module''' (rather than a CGI).

Tsala: admin settings moved to Performance settings

2011-10-19T15:06:16Z

admin settings moved to Performance settings

@@ Line 225: / Line 225: @@
 * [http://dev.mysql.com/doc/refman/5.0/en/server-parameters.html General advice on tuning MySQL parameters] (advice from the MySQL manual)
 * [http://www.mysqlperformanceblog.com/2007/11/01/innodb-performance-optimization-basics/ InnoDB performance optimization] taken from the [http://www.mysqlperformanceblog.com/ MySQL performance blog] site.
 ==Performance of different Moodle modules==

Tsala: performance template

2011-10-19T14:57:45Z

performance template

← Older revision		Revision as of 14:57, 19 October 2011
Line 1:		Line 1:
	{{~~Server settings}}~~		{{Performance}}
	~~{{Improve~~}}
	~~Location: ''Administration > Server > Performance''~~

	Moodle can be made to perform very well, at small usage levels or scaling up to many thousands of users. The factors involved in performance are basically the same as for any PHP-based database-driven system. When trying to optimize your server, try to focus on the factor which will make the most difference to the user. For example, if you have relatively more users browsing than accessing the database, look to improve the webserver performance.		Moodle can be made to perform very well, at small usage levels or scaling up to many thousands of users. The factors involved in performance are basically the same as for any PHP-based database-driven system. When trying to optimize your server, try to focus on the factor which will make the most difference to the user. For example, if you have relatively more users browsing than accessing the database, look to improve the webserver performance.

Line 270:		Line 267:
	==See also==		==See also==

	*[[Performance FAQ]]
	*Using Moodle: [http://moodle.org/mod/forum/view.php?f=94 Hardware and Performance] forum		*Using Moodle: [http://moodle.org/mod/forum/view.php?f=94 Hardware and Performance] forum

Line 279:		Line 275:
	* [http://moodle.org/mod/forum/discuss.php?d=88927 Comments on planned server hardware]		* [http://moodle.org/mod/forum/discuss.php?d=88927 Comments on planned server hardware]
	* [http://moodle.org/mod/forum/discuss.php?d=102978#p461624 Moodle performance in a pil by Martin Langhoff]		* [http://moodle.org/mod/forum/discuss.php?d=102978#p461624 Moodle performance in a pil by Martin Langhoff]
	~~[[Category:Performance]]~~

	[[es:Rendimiento]]		[[es:Rendimiento]]

Tsala: moved Performance to Performance recommendations

2011-10-19T14:56:42Z

moved Performance to Performance recommendations

← Older revision	Revision as of 14:56, 19 October 2011
(No difference)