You hit /index.php and save a couple miliseconds. No big deal right?

But keep in mind that that one index.php also loads usually around 30-60 CSS, JS, JPEG, PNG, GIF static files as well. You’re benchmark for static HTML seems to indicate nginx can server over 400 additional requests over apache. This is where nGinx will shine.

Additionally nginx has a much smaller memory footprint over apache. nginx processes usually take up like 4-9mB, where apache usually run up ~20mB. Also couple this with nginx the fact nginx serves requests quicker and thus processes close faster and you’ll save a tonne of memory.

If you want your pages (aka PHP pages) to be served faster, you need to install an opcache like APC. This will cache the compiled PHP after it’s first request and continue to server the cached opcode instead of compiling it on each request, significantly speeding requests up.

After that if you really want to speed up your WordPress, you should install WP-SuperCache, which caches full page requests as static HTML. Since we know nginx is much faster at serving these, you’ll get an even larger increase.

I would recommend implementing all these modifications along with nginx.

I would also recommend installing something to aggregate all your CSS and JS files into one large file. This will reduce the amount of requests per page and significantly reduce the load on your server and speed up how fast the page gets loaded on your readers browsers.

Also make sure gzip is enabled in nginx. This will compress CSS/JS/HTML before it gets sent to the browser (which will then decompress it) reducing the data send across the network and allow the browser to get at it much faster. It will also reduce the amount of bandwidth your site consumes.

wordpress 3.0 site:
Before: root@server:~# ab -n 100 -c 5 http://www.pepe.com/ (WP 3.0)
Requests per second: 8.42 [#/sec] (mean)
After: root@server:~# ab -n 100 -c 5 http://www.pepe.com/ (WP 3.0)
Requests per second: 8.46 [#/sec] (mean)

Simply HTML file with image:
Before: root@server:~# ab -n 100 -c 5 http://domain.com/test (a small HTML with a simply image)
Requests per second: 2373.49 [#/sec] (mean)
After:root@server:~# ab -n 100 -c 5 http://domain.com/test (a small HTML with a simply image)
Requests per second: 2786.91 [#/sec] (mean)

Also my tech guy says:

—- cut here —
You have tested it with just 5 concurrent connections, it is very low. The benefit of Nginx is ability to handle number of concurrent connections when
Apache will slow down a lot.

Example on one of our servers:
- -n 100 -c 5 nginx
Requests per second: 4.76 [#/sec] (mean)

- -n 100 -c 5 apache
Requests per second: 4.58 [#/sec] (mean)

- -n 2000 -c 100 nginx
Requests per second: 175.30 [#/sec] (mean)

- -n 2000 -c 100 apache
Requests per second: 101.09 [#/sec] (mean)

As you may see it is clear win. Of course, each site is individual, each usage are to be taken into consideration, etc.
But Nginx will perform better.

Your static site performs as follow:

nginx
Requests per second: 16801.75 [#/sec] (mean)

apache
Requests per second: 10690.25 [#/sec] (mean)

It is with 200 concurrent connections.

…with 500 apache started to die:
Requests per second: 15260.75 [#/sec] (mean)
Requests per second: 5082.34 [#/sec] (mean)

…and with 1000 connections:
Requests per second: 12964.08 [#/sec] (mean)
Requests per second: 8371.96 [#/sec] (mean)

Values are fluctuating a lot (e.g. it may be 12k as lowest for nginx, but never more than ~12k for apache)

So it all depends on the method of test (the load should be equal, etc.). Nginx will speed up on its caching as well. Even more, when it come to real
concurrency when you serve different sites at once it act even better.

Hope it helps you enjoy of Nginx more!
—- cut here —

Do you totally agree with him? I just wanted to load faster my webpages. My VPS is a hight hardware resources system and the only VPS in my main node (Inteli7 8 cores + 8GBs RAM DDR3)

Do you totally agree with it? I just want my webserver to make webpages load faster !!!