SuExec is for all CGI scripts (such as those coded in Perl or Python).Another question would be if suPHP is enabled, is there a need for suexec to be enabled?
SuExec is for all CGI scripts (such as those coded in Perl or Python).
SuPHP is only for PHP scripts not running as CGI (e.g. running as DSO, SuPHP).
Enabling SuPHP alone will not affect CGI Perl scripts running on your server.
Are there any improvements possible to speed up suPHP?
My server only contains my own sites (six so far). Lots of traffic and page views, but I suppose that makes for an easier load. I didn't see a huge improvement with DSO and eAccelerator, but it was a bit better. I killed it, because I didn't appreciate all the permissions headaches that were added in that environment.You do when you have a lot of accounts. In a shared environment I prefer suPHP. You stick the same setup on a system where Apache is running DSO with suHosin and eAccellerator and you see a tremendous difference in speed. I understand suPHP is much slower but I would like to improve it just a little better in performance. A caching system, tweaks whatever but it appears there is very little information out there on this.
I'm fairly certain that eAccelerator, APC, and XCache all have to be ran in a persistent environment (dso, fastcgi) to have any effect at caching.Anything out there to speed up suPHP? eAccellerator work yet? FastCGI, etc?
How about suggesting an Easy Apache configuration that might be suitable?I'm fairly certain that eAccelerator, APC, and XCache all have to be ran in a persistent environment (dso, fastcgi) to have any effect at caching.
The worst part of suPHP is the overhead you incur whilst creating a new process for each execution. You might look into using FastCGI, it takes a little bit of work since cPanel uses a very basic and insecure configuration, but the benefits are worth it in the end.
I agree. Should we be choosing FastCGI instead of suPHP, and would that give us the option of moving to eAccelerator within a "persistent environment"?I am a bit confused. I do see a lot of threads of using suPHP and FastCGI together. This does not appears possible with easyApache. You can install both but when you select the mode in which PHP runs, you have DSO, FastCGI and suPHP all as separate options. When suPHP is selected there is no reference to FastCGI or fcgi in the Apache conf files.
The more I read the more it looks there are a lot of confused people out there and FastCGI is to be used completely separate from suPHP. With some tweaks it provides the security of suPHP but is a bit faster.
SuPHP and FastCGI are not even remotely the same thing and noThe more I read the more it looks there are a lot of confused people out there and FastCGI is to be used completely separate from suPHP. With some tweaks it provides the security of suPHP but is a bit faster.
|Thread starter||Similar threads||Forum||Replies||Date|
|C||Php-fpm & cgi vs suPHP||Web Servers and Applications||3|
|J||suPHP and file ownership by FTP||Web Servers and Applications||9|
|O||Will not having a suPHP_ConfigPath in my .htaccess file prevent migration from EasyApache3 to EasyApache4?||Web Servers and Applications||4|
|mod_ruid2+jail apache vs suphp (security)||Web Servers and Applications||1|
|P||SOLVED PHP FPM and SuPHP/Fastcgid||Web Servers and Applications||5|