|For many people who are using suPhp, they may want to consider CustomBuild 2.0 with mod_php+mod_ruid2 as a replacement.|
Both setups will run php as the User.
Here are a few comparisons.
1) Disk I/O
For each Apache request to a php file, suPhp must read in the php binary, all of it's included libraries.
mod_php is already loaded as an Apache module, so the load of these binaries is not required.
Because of somewhat standalone nature of suPhp, it doesn't allow for modifications of php settings in .htaccess files or httpd.conf files. Changes can be made on a per-domain basis using per-User php.ini files, but this might be somewhat overkill to try and manage.
Because each request of suPhp is a brand new process, shared memory cannot be used. As such, performance cache modules like opCache do not work with suPhp. Because mod_php can use persistent shared memory, opCache does work. The benefits of opCache are to store php files in memory, saving the need for multiple reads, but to also store it's compiled state in memory, so each php request needs to only execute. No reading or compiling are needed. This has a bonus side-effect of reducing your disk I/O (as the cost of some ram)
|How to upgrade to CustomBuild 2.0|
|Installing php OpCache with CustomBuild 2.0|
|I'd like the default apache, and php settings for CustomBuild 2.0|
© 2018 JBMC Software, Suite 173 3-11 Bellerose Drive, St Albert, AB T8N 1P7 Canada. Mon-Fri 9AM-5PM MST