New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
I'd suggest staying on the tried and true path, using either mod_php or PHP-FPM, if you're looking at the available options out there. The best performance gains you can attain in setting up a LAMP stack (or any of the common derivatives):
op-code caching: It more or less compiles your code into machine code (similar to compiling Java), such that subsequent requests to a script can be served quicker.
caching dynamic content: If you can, avoid expensive operations like queries to the database, writing files to disk, etc. A commonly used tactic is to cache content when possible. Does every request for a blog post require running a hundred different queries against a database? Probably not. We could cache some of that data once fetched, and serve it to anyone who fetches that page subsequently.
php 5.3.3 + mod_php ruid2 + xcache
php 5.3.3 + mod_php + xcache
which is better performance ?
ruid2 hasn't been thoroughly vetted for security (its last change, 2 months ago, was a security fix, and it hasn't made its way to the sourceforge repo yet). I wouldn't trust it, and would stick with plain old mod_php without the ruid2 module.
suphp is better.
SuPHP is nice, but it has been EOLed, and is no longer supported.