Restricted only in Windows with Php,nginx is not considered, too weak; Swoole also no win version
My idea is that the IIS7.5,OP cache has wincache, fortunately Redis/memcache has a win version available
The other one is apache+mod_fpm/mod_fastcgi,win, it should be fcgi way faster.
By the way, if it's pure HTML, which Web server is best? If the above performance is not enough, it may generate a pure HTML way
Reply content:
Restricted only in Windows with Php,nginx is not considered, too weak; Swoole also no win version
My idea is that the IIS7.5,OP cache has wincache, fortunately Redis/memcache has a win version available
The other one is apache+mod_fpm/mod_fastcgi,win, it should be fcgi way faster.
By the way, if it's pure HTML, which Web server is best? If the above performance is not enough, it may generate a pure HTML way
Kangle is not bad, too.
The official PHP Zendopcache also supports Windows and does not require the use of wincache.
The Windows versions of Redis and memcached are provided by third parties and are not officially supported by redis/memcached.
Swoole can also run on windows in a Cygwin environment.
Comparison of IIS and Apache performance tests on Windows 7
Environment (64-bit Win7): iis7+php5.4 (NTS non-thread-safe version) vs Apache2.4 (32-bit) +php5.4
Static file Processing:
Ab-k-c100-n10000 http://127.0.0.1/info.htm # IIS RPS 1709
Ab-k-c100-n10000 http://127.0.0.1:8080/info.htm # Apache RPS 1847
Conclusion: Apache based on Apr runtime and Winnt Multi-threading is no worse than IIS in static resource processing.
PHP file Processing:
Ab-k-c100-n10000 http://127.0.0.1/bs.php # IIS RPS 1180
Ab-k-c100-n10000 http://127.0.0.1:8080/bs.php # Apache RPS 1071
Conclusion: Apache uses threaded MPM, so a thread-safe version of PHP is required, and thread safety checks have some overhead, so performance is lower than iis+php-cgi.
In a iis7+php phpinfo () test, 100 concurrent, 10,000 requests, incredibly 8,978 requests failed!
However, how much is the volume of visits? What kind of Web site is it?
I want to know how the nginx is too weak ...
Too many pits. Our company used a few years of win. Iis. Php.
This month decided to move to Liunx. The main is a website on IIS constantly error. The customer has already called the phone to explode. Finally, migrate to Liunx. Problem solving. The boss decided never to win the server again. Come out of the pit early. I'm out of the question. It's too late to cry.