Should I use FastCGI or SuPHP for my VPS?

I have VPS running Centos and installing cpanel. 2 GB of RAM.

Apache 1.3.42 is currently running. I could also use 2.0.64 or 2.2.22, should I upgrade?

PHP (5.3) works like SuPHP.

I am wondering if I should adhere to the current setting? Or should I use FastCGI and use the cache option code PHP (APC, XCache, etc.)?

I would like to use the operation cache code, if possible, to speed up my page generation time, however I read that running FastCGI on VPS can increase the load on the server.

What are the security implications of SuPHP compared to FastCGI?

+4
source share
2 answers

Typically, the FastCGI PHP handler serves PHP requests faster than suPHP. FastCGI is usually good if you want to reduce CPU usage. It uses a FREE RAM server that stores PHP scripts in memory instead of starting a separate PHP process for each incoming PHP request. In other words, unlike suPHP, FastCGI does not require the execution of a single PHP process per PHP request. However, there are some drawbacks to this approach, as a rule, FastCGI works intensively in memory, because it supports PHP sessions that are open in the background in RAM, for faster access. The FastCGI PHP handler is ideal when you have enough free RAM available and you have encountered excessive PHP execution requests due to suPHP handlers.

+1
source

I would recommend the FastCGI PHP handler as FastCGI a faster way to serve PHP requests than using suPHP. FastCGI is good at reducing CPU usage by using your server in RAM to store PHP scripts in memory instead of running a separate PHP process code for every PHP request. The main advantages are processor performance and the ability to use opcode caching.

0
source

All Articles