• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Question Change PHP-FPM settings

KZM

Basic Pleskian
Hi there!

I'm tuning my Apache server bc of it is continuously being rebooted due to timeouts.

As I'm using PHP handler FPM I have found some settings I can tweak (I've already upgraded my VPS to 16 GM memory)
File: ../mods-available/mpm_prefork.conf
1
2
3
4
5
6
7
<IfModule mpm_prefork_module>
StartServers 4
MinSpareServers 20
MaxSpareServers 40
MaxRequestWorkers 200
MaxConnectionsPerChild 4500
</IfModule>

But also in Plesk UI I noticed these same settings can be tweaked.

So the questions is WHERE do I make these tweaks?
 
@KZM You're confusing two different things. The one in your first post refers to web server settings, the other one you refer to in your PHP-FPM sreenshot refers to PHP settings. For most scenarios the PHP-FPM setting "on demand" is a good choice. If the "max_children" value is too small, it is possible that additional requests cannot be processed until a previous request has finished processing. This however will be logged in your error_log, so you should get a clear message like "max_children reached". A web server with max_request works = 200 should definitely be able to handle all. Having 20 server instances "ready to go" is also enough for most cases. So probably you're exceeding the PHP-FPM settings. Try a larger numbre of max_children, e.g 50, and a high number of max_requests, e.g. 10000.
 
@KZM You're confusing two different things. The one in your first post refers to web server settings, the other one you refer to in your PHP-FPM sreenshot refers to PHP settings. For most scenarios the PHP-FPM setting "on demand" is a good choice. If the "max_children" value is too small, it is possible that additional requests cannot be processed until a previous request has finished processing. This however will be logged in your error_log, so you should get a clear message like "max_children reached". A web server with max_request works = 200 should definitely be able to handle all. Having 20 server instances "ready to go" is also enough for most cases. So probably you're exceeding the PHP-FPM settings. Try a larger numbre of max_children, e.g 50, and a high number of max_requests, e.g. 10000.
Thanks! but do those 2 affect each other?
 
Back
Top