Performance recommendations: Difference between revisions
Dan Stowell (talk | contribs) No edit summary |
Dan Stowell (talk | contribs) No edit summary |
||
Line 1: | Line 1: | ||
Large installations tend to separate the web server and database onto separate servers, although for smaller installations this is typically not necessary. | Large installations tend to separate the web server and database onto separate servers, although for smaller installations this is typically not necessary. | ||
The consensus in the Moodle community seems to be that a Linux-based webserver running Apache, with PHP installed as well as a PHP accelerator, is commonly the best choice. | |||
It is possible to load-balance a Moodle installation, for example by using more than one webserver if necessary. 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). | |||
==== Web server performance ==== | ==== Web server performance ==== |
Revision as of 13:04, 22 January 2006
Large installations tend to separate the web server and database onto separate servers, although for smaller installations this is typically not necessary.
The consensus in the Moodle community seems to be that a Linux-based webserver running Apache, with PHP installed as well as a PHP accelerator, is commonly the best choice.
It is possible to load-balance a Moodle installation, for example by using more than one webserver if necessary. 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).