However, it is not a multi-threaded operation. Processes can be easily spread out by the OS to use all cores. Prefork gives you a separate process for every request. The most common MPM is prefork (mpm_prefork). How Apache works on multi-core systems and how you configure it is greatly influenced by which Multi-Processing Modules (MPM) you use. As long as you don’t limit Apache to use fewer cores than you have in the server, there’s no other action you need to take. By default, Apache (and any other multi-process application) will use all available cores as possible. To configure Apache to use more of your CPUs, you need to get rid of the bottle-neck that prevents Apache from using more CPUs. This blog post will be focusing on maximizing the Linux server resources for your Moodle installation, especially on the primary resources like CPU, memory and disks. For example, a 4-core proxy server is only using not more than a single core the whole time, a database server with 64GB RAM in total but only used up to 16GB of RAM, leaving 48GB of free memory and many more such cases that fundamentally wasting the precious resources. We have seen some production setups and we can tell that some of the resources are underutilized. For bare-metal servers, the hardware resources are usually fixed with anticipation of maximum performance, but the next question is how are we going to maximize the server resources to their full potential. This is not an easy task, and it requires a lot of ongoing tuning until the server is stable. To run a clustered Moodle system efficiently, one has to allocate sufficient resources to the essential services required by Moodle.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |