It’s important to note that the handling and dispatching system for basic requests varies across different PHP application servers, resulting in the utilization of different directives. However, despite these variations, the functionality of these parameters often remains similar. To explore the detailed directives relevant to a particular application server, please refer to the corresponding section outlined below.<\/p>\n
- \n
- Apache PHP<\/a><\/li>\n
- NGINX PHP<\/a><\/li>\n<\/ul>\n
Additionally, you have the option to learn about How the auto-configuration works<\/a>.<\/p>\n
Alternatively, if you prefer to manually redefine the values, you can proceed to the section titled How to Disable the Automatic Optimization<\/a> in this guide.<\/p>\n
Apache PHP Auto Adjustable Settings<\/h2>\n
Dynamic request handling in Apache PHP is facilitated through the utilization of the prefork<\/strong> Multi-Processing Module (MPM). This module optimizes server performance by fully utilizing its potential. The directives related to MPM can be found in the main Apache configuration file located at \/etc\/httpd\/conf\/httpd.conf<\/strong>.<\/p>\n
![\"Apache](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/httpd.conf_.png\" "\\"Apache")
<\/a><\/p>\nBelow is a comprehensive list of parameters that the platform configures for the prefork<\/strong> module:<\/p>\n
- \n
- StartServers:<\/strong> This parameter sets the number of child server processes created during startup.<\/li>\n
- MinSpareServers (MaxSpareServers):<\/strong> These parameters define the minimum (maximum) number of server processes to be kept in reserve to handle incoming requests efficiently.<\/li>\n
- ServerLimit:<\/strong> This parameter sets the maximum allowed value for the MaxRequestWorkers directive, effectively limiting the number of simultaneous requests that can be processed by the server.<\/li>\n
- MaxRequestWorkers:<\/strong> Configuring this parameter determines the maximum number of simultaneous requests that the server can handle efficiently.<\/li>\n
- MaxConnectionsPerChild:<\/strong> This parameter defines the maximum number of requests that a single child process can serve before it is terminated and replaced with a new one.<\/li>\n<\/ol>\n
Based on the allocated resources, such as the number of dynamic cloudlets reserved for the Apache PHP server, and the capacity of the CPU provided by your hosting provider, AccuWeb.Cloud automatically adjusts the ServerLimit<\/strong> and MaxRequestWorkers<\/strong> parameters.<\/p>\n
![\"Apache](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/Apache-Prefork-Module-Configs.png\" "\\"Apache")
<\/a><\/p>\nMaxRequestWorkers<\/strong> = ServerLimit<\/strong> = min( {containerRam<\/strong>} \/ 30MiB, {coresCount<\/strong>} * 5 )<\/p>\n
As per this statement, both directives are set equal to the lower value between:<\/p>\n
- \n
- The amount of RAM allocated to the node, divided by 30.<\/li>\n
- The number of cores on the hosting provider’s physical server where the container is located, multiplied by 5.<\/li>\n<\/ol>\n
In this manner, the parameters are dynamically adjusted based on the number of allocated cloudlets, ensuring they do not exceed the hardware limits.<\/p>\n
\nNote:<\/strong> If you choose to specify custom values for these directives, it’s important to exercise caution as incorrect values can lead to instability in your Apache PHP server:<\/p>\n- \n
- Setting ServerLimit<\/strong> too high may result in the allocation of unused shared memory, while setting it too low may limit the server’s performance potential.<\/li>\n
- Ensure that MaxRequestWorkers<\/strong> is set to accommodate the expected number of simultaneous requests while also being mindful of available RAM to prevent memory issues.<\/li>\n<\/ul>\n<\/div>\n
<\/div>\nYou might also want to check out how the auto-configuration operates or learn how to disable automatic optimization<\/a> if you’re inclined to set custom values for these directives.<\/p>\n
<\/div>\n\t\t\n\t\t\t\n \n \n\n\n \n \t\t\n\t\t\t\t\n\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t <\/div>\n <\/div>\n <\/div>\n <\/section>\n \t\t<\/div>\n\t\t\n<\/div>\nNGINX PHP Auto Adjustable Settings<\/h2>\n
Request handling in the NGINX PHP application server is managed by the FastCGI Process Manager (FPM), which can be configured via the \/etc\/php-fpm.conf<\/strong> file. This file is automatically added to the favorites list in the container file manager for easy access.<\/p>\n
![\"NGINX](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/NGINX-PHP-php-fpm.conf_.png\" "\\"NGINX")
<\/a><\/p>\nBy default, FPM operates in the ondemand<\/strong> mode, as specified by the “pm<\/strong>” directive. In this mode, FPM spawns new processes as needed (i.e., on demand) and removes idle ones. The key parameters for this mode are:<\/p>\n
- \n
- pm.max_children:<\/strong> This parameter defines the maximum number of child processes. It is typically set equal to the number of CPU cores available for the container, with a minimum value of 2.<\/li>\n
- pm.process_idle_timeout:<\/strong> This parameter sets the delay before killing an idle process, with a default value of 60 seconds.<\/li>\n<\/ol>\n
![\"NGINX](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/NGINX-PHP-ondemand.png\" "\\"NGINX")
<\/a><\/p>\n\nTip:<\/strong> The precise value of the pm.max_children parameter is influenced by the CPU capacity provided by your hosting provider and the number of allocated cloudlets for your container. Consequently, increasing the count of cloudlets automatically adjusts the pm.max_children<\/strong> parameter.<\/p>\nIf you wish to define this directive explicitly without disabling the automatic optimization, you can utilize the appropriate PHPFPM_MAX_CHILDREN<\/strong> variable.<\/div>\n
<\/div>\nIf necessary, you have the option to disable the automatic optimization to change the FPM mode and adjust other directives. However, it’s crucial to exercise caution as incorrect values can lead to instability in your NGINX PHP server.<\/p>\n
For enhanced performance, the PHP-FPM listener uses a UNIX domain socket instead of the standard TCP socket. This approach is better suited for communication within the same host, as it bypasses certain checks and operations like routing, ultimately improving efficiency.<\/p>\n
<\/div>\n\t\t\n\t\t\t\n \n \n\n\n \n \t\t\n\t\t\t\t\n\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t <\/div>\n <\/div>\n <\/div>\n <\/section>\n \t\t<\/div>\n\t\t\n<\/div>\nHow the PHP Auto-Configuration Works<\/h2>\n
You can observe how the parameters mentioned above are adjusted based on the allocated resources. Let’s take the example of the Apache PHP server:<\/p>\n
1.<\/strong> Begin by creating a new PHP environment with the Apache PHP<\/strong> application server inside, if you haven’t already done so.<\/p>\n
Next, navigate to the Config<\/strong> button for this node and locate the prefork<\/strong> module configurations in the \/etc\/httpd\/conf\/httpd.conf<\/strong> file.<\/p>\n
![\"Prefork](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/Prefork-Module.png\" "\\"Prefork")
<\/a><\/p>\nTake note of the directive values corresponding to the current number of cloudlets.<\/p>\n
2.<\/strong> Proceed to adjust the resource limit for the Apache PHP server using the “Change Environment Topology<\/strong>” button. Afterward, refresh the \/etc\/httpd\/conf\/httpd.conf<\/strong> file and compare the prefork parameter values with the ones previously recorded.<\/p>\n
![\"Prefork](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/Prefork-Parameter-Values.png\" "\\"Prefork")
<\/a><\/p>\nIndeed, the directive values increased automatically as a result of a higher amount of available resources being allocated, demonstrating that the automatic optimization is functioning. Similarly, if the cloudlets count were to be decreased, the values of these parameters would be reduced accordingly.<\/p>\n
Disable Automatic Optimization<\/h2>\n
If you wish to specify your own custom values rather than relying on the automatically configured directives, it’s necessary to disable the automatic optimization. Otherwise, any custom changes you make will be reverted during container restart or updates.<\/p>\n
To manually modify any of the auto-configured settings, you can set the JELASTIC_AUTOCONFIG<\/strong> environment variable<\/a> to false.<\/p>\n
\nNOTE:<\/strong> Please note that applying inappropriate directive values may lead to instability in your server. Therefore, it is strongly advised not to make manual changes unless you are fully confident in what you are doing.<\/div>\n<\/div>\nLegacy Implementation<\/h3>\n
For legacy implementations on old containers, you simply need to remove the line containing the optimization mark at the beginning of the relevant configuration file:<\/p>\n
For Apache PHP<\/strong>, locate and delete the line “# Jelastic autoconfiguration mark” within the \/etc\/httpd\/conf\/httpd.conf<\/strong> file.<\/p>\n
- pm.process_idle_timeout:<\/strong> This parameter sets the delay before killing an idle process, with a default value of 60 seconds.<\/li>\n<\/ol>\n
- Ensure that MaxRequestWorkers<\/strong> is set to accommodate the expected number of simultaneous requests while also being mindful of available RAM to prevent memory issues.<\/li>\n<\/ul>\n<\/div>\n
- Setting ServerLimit<\/strong> too high may result in the allocation of unused shared memory, while setting it too low may limit the server’s performance potential.<\/li>\n
- MinSpareServers (MaxSpareServers):<\/strong> These parameters define the minimum (maximum) number of server processes to be kept in reserve to handle incoming requests efficiently.<\/li>\n
- NGINX PHP<\/a><\/li>\n<\/ul>\n
![\"Remove](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/Jelastic-autoconfiguration-mark.png\" "\\"Remove")
<\/a><\/p>\n![\"Remove](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/php-fpm.conf-File.png\" "\\"Remove")
<\/a><\/p>\n