我已经找了好几天了，看看是否有人在之间做了很好的、有文档记录的PHP处理速度比较
- apache mpm prefork 2.4与mod_php 5.4
和
- nginx 1.2.x+PHP-FPM 5.4
我为什么要看：我看到的唯一测试是abount基准测试，提供完整的页面或类似Hello，World的测试，没有关于测试内容的适当文档。我不在乎请求/秒，硬件，但我确实需要看看测试了什么PHP脚本，以及使用了什么确切的配置。
为什么这两个：mod_php被认为是处理php最快的（没有静态文件，没有请求/响应测量，只处理php本身），但从那以后发生了很多变化，包括apache版本。Nginx和PHP-FPM占用的内存要少得多，所以这是更改架构的一个很好的理由，但如果它们在这种情况下不够快，那么更改就无关紧要了。
我知道如果我找不到，我必须自己做，但我不敢相信到目前为止还没有人做过这样的测试：）
我已经在CentOS 6.3上使用nginx 1.2.7、apache 2.4.3和php 5.4.12完成了此测试，所有这些都是在不更改默认值的情况下编译的。
./configure
make && make install
除了php，我启用了php fpm
./configure --enable-fpm
除以下说明外，所有服务器都有100%的默认配置。所有测试都是在测试服务器上完成的，没有负载，测试之间需要重新启动。服务器具有Intel（R）Xeon（R）CPU E3-1230、1GB RAM和RAID 1中的2 x 60GB SSD。使用ab -n 50000 -c 500 http://127.0.0.1/test.php 进行测试
测试PHP脚本：
<?php
$testing = 0;
for ($i = 0; $i < 1000; $i++) {
$testing++;
}
echo $testing;
我还必须在nginx.conf中启用php，因为它在默认情况下没有启用。
location ~ .php$ {
fastcgi_pass 127.0.0.1:9000;
fastcgi_index index.php;
fastcgi_param SCRIPT_FILENAME /var/www/html$fastcgi_script_name;
include fastcgi_params;
}
Nginx-127.0.0.1:9000 上的PHP-FPM
Concurrency Level: 500
Time taken for tests: 10.932 seconds
Complete requests: 50000
Failed requests: 336
(Connect: 0, Receive: 0, Length: 336, Exceptions: 0)
Write errors: 0
Non-2xx responses: 336
Total transferred: 7837824 bytes
HTML transferred: 379088 bytes
Requests per second: 4573.83 [#/sec] (mean)
Time per request: 109.317 [ms] (mean)
Time per request: 0.219 [ms] (mean, across all concurrent requests)
Transfer rate: 700.17 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 34 338.5 0 7000
Processing: 0 34 166.5 23 8120
Waiting: 0 34 166.5 23 8120
Total: 13 68 409.2 23 9846
Percentage of the requests served within a certain time (ms)
50% 23
66% 28
75% 32
80% 33
90% 34
95% 46
98% 61
99% 1030
100% 9846 (longest request)
Nginx-通过套接字的PHP-FPM（配置更改为fastcgi_pass）
fastcgi_pass unix:/var/lib/php/php.sock;
Concurrency Level: 500
Time taken for tests: 7.054 seconds
Complete requests: 50000
Failed requests: 351
(Connect: 0, Receive: 0, Length: 351, Exceptions: 0)
Write errors: 0
Non-2xx responses: 351
Total transferred: 7846209 bytes
HTML transferred: 387083 bytes
Requests per second: 7087.70 [#/sec] (mean)
Time per request: 70.545 [ms] (mean)
Time per request: 0.141 [ms] (mean, across all concurrent requests)
Transfer rate: 1086.16 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 26 252.5 0 7001
Processing: 0 24 112.9 17 3683
Waiting: 0 24 112.9 17 3683
Total: 7 50 306.4 17 7001
Percentage of the requests served within a certain time (ms)
50% 17
66% 19
75% 20
80% 21
90% 23
95% 31
98% 55
99% 1019
100% 7001 (longest request)
Apache-mod_php
Concurrency Level: 500
Time taken for tests: 10.979 seconds
Complete requests: 50000
Failed requests: 0
Write errors: 0
Total transferred: 9800000 bytes
HTML transferred: 200000 bytes
Requests per second: 4554.02 [#/sec] (mean)
Time per request: 109.793 [ms] (mean)
Time per request: 0.220 [ms] (mean, across all concurrent requests)
Transfer rate: 871.67 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 22 230.2 1 7006
Processing: 0 58 426.0 18 9612
Waiting: 0 58 425.9 18 9611
Total: 5 80 523.8 19 10613
Percentage of the requests served within a certain time (ms)
50% 19
66% 23
75% 25
80% 26
90% 31
95% 36
98% 1012
99% 1889
100% 10613 (longest request)
我非常乐意进一步调优apache，但apache似乎跟不上了。明显的赢家是通过socket使用php-fpm的nginx。
你似乎在比较苹果和橙子，或者更准确地说，你通过调整两个变量来混淆结果。当然，将Apache+fastcgi+php-fpm与nginx+php-fdm进行比较会更明智吗？您希望php-fpm部分是相同的，因此您将衡量Apache_fastcgi与nginx的优劣。