stay far from suphp !!

I moved from apache 1.3 and php 5.2.5 with eaccelerator to
apache 2.2 with php 5.2.5 and suphp

With apache 1.3 php 5.2.5 and eaccelerator my system load was rarely higher than 1.
With apache 2.2/suphp my server load medium value was 6 (yes 6) and all the days the server was crashing ..

I returned to apache dso with eaccelerator without suphp .. All works excellent now such as before ..
Especially disabling suphp the %system usage reported by "sar" passed from a medium of 30% to only 7% !!

If you have an old slow server stay FAR from suphp , it will mutiple your server load !!.


The solution to solve all the problems with php , python , perl ... is chorooting users .
Unluckly whm looks always at the easy way (phpsuxec , suphp...) but these solutions
are not good and causes only problems to us . I truly hope WHM will decide a day (version 12?)
to chroot users , so will not have more worries about php safe mode , suphp , openbase dir , suexec ..... and countless problems with python
,ruby on rails , perl , php ...

 

Do you have an old pentium 4 with 1 GB of ram ? If yes , try to use suphp and see what happens.
On fast server the problem is not visible , on al old server yes.

 

well on a server with pentium 4 and 150 account you will see the difference , and it's a big diffrence .

 

>
So the fact with suPHP it's spawning PHP processes due to the PHP being a CGI may have something to do with such an increased load average
>

exactly . This is well visible on older server. Of course if you have quad core processors you can't notice the difference (you may notice it using a good benchmark).

>
If I try to use EAccelerator with suphp, I'll let you know my results.
>

EAccelerator with suphp will not work ! Any php accelerator on the planet does not work with suphp . If someone will not create in the future some accelerator which works with suphp no accelerator currently can work with suphp. I think that suhosin well configured (whm does not configure it!) can give the same (and perhpas better) security than suphp . With suhosin I am using eaccelerator/zend 3.3.0 and it works very very well . Also eaccelerator should be configured/tweaked a little on php.ini . I am using it with 128 MB ram and it works really good , server load rarely over 1.

 

I did not install suphp with eaccelerator someone else suggested this. On the countrary if you read my post above I explain that it's not possible to install a php accelerator with suphp (an existent php accelerator , probably in the future someone will code an accelerator for suphp too).

suphp overheads exists compared with DSO , simply these are not visible on a powerful machine.
On a slow machine (old hardware with big traffic) the difference between DSO and suphp is well visible . So the title should be changed in this way "stay far from suphp if you have an old server with big traffic" .

 

also if you see eaccelerator loaded using php -v

it does NOT mean that eaccelator is working !!!!

Install the eaccelator admin interface (each php accelerator can install an admin interface), and look if it's caching files . Well you'll see from eaccellator admin that it's NOT caching files , because eaccelerator can't work with cgi.