Answered

FPM IS FastCgi ! “F.P.M.” stands for “FastCGI Process Manager”

CGI is really slow. FastCGI, as its name indicates… Is not slow. CGI
is slow for the simple reason you have to completely launch PHP and all
its libraries & etc. … whenever FastCGI launches “hanging” PHP
processes that are waiting for requests to spend their time doing
something more useful than “hanging” in memory

But this is the very fact why there is currently a problem with running
many websites with FastCGI : it’s memory consuming if you have so many hanging processes waiting for queries (as a php process is ~ 15MB, and even more when parsing a wordpress website ! (~35MB !) ).

(note : “hanging” here does not mean the unix “hang” signal, huh, it
just means hanging as anything in real life)

After you are done installing nginx, php, and mysql, there are some php extensions you need to be installed, such as php-mbstring, php-mcrypt.

# yum –enablerepo=webtatic install php-mbstring

# yum –enablerepo=webtatic install php-mcrypt

# yum –enablerepo=webtatic install php-gd

# service php-fpm restart

That’s all needed for php-extension, but if you want to install another extension do as above script but replace the extension with the one you want to install.

nginx ( pronounced “engine X” ) is a high-performance, lightweight, ease-to-use Web server/reverse proxy and email proxy.
Nginx is licensed under BSD-like license, and free to use.
Nginx is support on various OS Platform such GNU/Linux, UNIX, Mac OS X,BSD variants, Microsoft Windows and Solaris System compiled into different packages.

Nginx is very fast to deliver web page content with very efficient use of system resources. Support on dynamic HTTP content using FastCGI handles, and can serve and very well as software load-balancer.

Nginx is well recommended to serve a high-scale traffic with high concurrent users.
Nginx was developed to accomodate the needs of various websites run run by Rambler, for which it was serving 500 million requests per day as of September 2008.

Nginx is great, but if you want to stick with Apache, it’s possible to slim it down quite a bit from the default settings:

* Use the worker MPM rather than prefork (with worker MPM Apache no longer has a “process per connection” model).
* Look at all the shared modules you’re loading, get rid of any that you don’t need.
* Avoid embedding application servers inside Apache (i.e. mod_python, mod_php, etc) if you can avoid it. Instead, run application servers in a separate process and have Apache proxy to them (i.e. for Python code use mod_wsgi in daemon mode). This way your Apache threads that are simply serving static content won’t be unnecessarily bloated.
* In your Apache config, reduce the StartServers, MaxClients, MinSpareThreads, and MaxSpareThreads settings. Depending on your expected load you can sometimes reduce them by a factor of five or more from the default settings.