I *think* inside the php settings for the individual hosting instance theres a restart/stop/start set of icons.In case of service crash, do you know how to restart PHP-FPM for a specific website or should we restart the whole service?
This is the biggest issue I have with it. As a hosting company you have small hostings and big (expensive) hostings. but even the smalles hosting can now use a dedicated pool for its page - and there is no option to deny this. the only option is to disable it for all. in the end we had to do it and lost an option for our high tier customers.I just discovered that even customers can choose this new dedicated PHP-FPM handler.
What does that mean for the server load and memory usage? Does anyone have experience with this?
Can this function be disabled for customers?
You could solve this by creating a different 'service plan' in Plesk for your 'lower tier' customers and disable the 'PHP version and handler management' permission for this server plan. Which will disable the option for customers to change the PHP handler and PHP version. Or even create a Service Plan Add on which disable the 'PHP version and handler management' permission.This is the biggest issue I have with it. As a hosting company you have small hostings and big (expensive) hostings. but even the smalles hosting can now use a dedicated pool for its page - and there is no option to deny this. the only option is to disable it for all. in the end we had to do it and lost an option for our high tier customers.
I know that. I am using PLESK on a daily basis and since many many years. But currently i can not allow a customer to change its php version but deny selection the handler. all i can do is forbidding all, and write an own plugin to allow parts of it, namely the php version selection. a dedicated pool is a sales factor. why should someone give low tier customers a dedicated pool which creates an overhead on the server without getting adequately paid for it. so lower tiers should have php version selector but not php handler selector.The dedicated PHP-FPM handlers are just an addition to the already available PHP handlers. If you don't want to make them available to (all of) your customers disable the 'PHP version and handler management' permission. What else does there need to be 'customized'? The options are already available in Plesk. You just have to utilize them.
Just the FPM for the pool - it's dependent.In case of service crash, do you know how to restart PHP-FPM for a specific website or should we restart the whole service?
It's fine - the overhead on CPU/memory is generally minimal. You get the benefit of "better" isolation, plus unique OpCache pools for each site.I just discovered that even customers can choose this new dedicated PHP-FPM handler.
What does that mean for the server load and memory usage? Does anyone have experience with this?
# sudo plesk bin php_handler --list | grep -E plesk.*fpm | awk -F" " '{ print $1 }'
plesk-php73-fpm
plesk-php73-fpm-dedicated
plesk-php74-fpm
plesk-php74-fpm-dedicated
# systemctl status plesk-php74-fpm-dedicated
Unit plesk-php74-fpm-dedicated.service could not be found.
# ls /usr/lib/systemd/system/*.service | grep plesk-php
/usr/lib/systemd/system/plesk-php73-fpm.service
/usr/lib/systemd/system/plesk-php74-fpm_domain.com_0.service
/usr/lib/systemd/system/plesk-php74-fpm.service
/usr/lib/systemd/system/restart-plesk-php74-fpm.service
# cat /usr/lib/systemd/system/restart-plesk-php74-fpm.service
[Service]
ExecStart=/bin/systemctl try-restart plesk-php74-fpm_*
@john0001 disagree with "It's fine - the overhead on CPU/memory is generally minimal."
We've turned this on for higher tier customers and definitely significant boost in speed as they're not waiting for free workers but its also jacked up short term average CPU utilisation by 20-30% because more peak CPU is available to be used.
To add the PHP handler as a dedicated application, append '-fpm-dedicated' to the hander ID when registering;