I presently have one server with nginx that reverse_proxy to apache (same server) for processing php demands. I am wondering basically drop apache so I'd run nginx/fastcgi to php if I'd use whatever kind of performance increases. I am presuming I'd since Apache's pretty bloated up, but simultaneously I am unsure how reliable fastcgi/php is particularly in high traffic situations.

My sites will get about 200,000 unique site visitors per month, with around 6,000,000 page crawls in the search engines like google monthly. The dpi is continuously growing so I am searching at perfomrance options.

My website is extremely enhanced code smart there is not any caching (do not want that either), each page includes a max of two sql queries with no joins on other tables, indexes are great too.

Each year approximately I'm going to be spinning everything to make use of ClearSilver for that templates, after which most likely use python otherwise c++ for extreme performance.

I guess I am pretty much searching for any advice from anybody who knows nginx/fastcgi and when prepared to provide some benchmarks. My sites is one server with 1 quad core xeon, 8gb ram, 150gb velociraptor drive.

nginx will certainly speed up than Apache. I can not tell about fastcgi since i have not used at all it with nginx but this solution appears to be preferable on several servers (one for static contents and something for fastcgi/PHP).

If you're really focusing on performance -as well as consider C/C++- then you definitely should provide a attempt to G-WAN, an exciting-in-one server which supplies (extremely fast) C scripts.

Not just G-WAN includes a absurdly small memory footprint (120 KB) however it scales like little else. There's work in front of you should you migrate from PHP, but you can begin using the performance-critical tasks and migrate progressively.

We now have made the jump and can't consider to return to Apache!

This is a chart showing the particular performances of nginx, apache and g-wan:


apache doesn't appear to guide those (and that is a -Quad XEON @ 3GHz).

Here's a completely independent benchmark for g-wan versus nginx, varnish yet others http://nbonvin.wordpress.com/2011/03/14/apache-versus-nginx-versus-varnish-versus-gwan/

g-wan handles a lot more demands per second with a smaller amount CPU time.