Between these projects there are significant differences that can affect the performance, opportunities and implementation time required to implement and launch each of the solutions. The choice is a series of compromises and do not neglect the tests. Ultimately, there is no one universal web server for all possible tasks, so it is important to find the solution that best suits your goals and objectives. Nginx knows 99% of everything that the modern market needs for productive work.
Basic tests show the following: Apache + mod_php
Total transferred: 3470000 bytes
HTML transferred: 120000 bytes
Requests per second: 2395.73 [# / sec] (mean)
Time per request: 4.174 [ms] (mean)
Time per request: 0.417 [ms] (mean, across all concurrent requests)
Transfer rate: 811.67 [Kbytes / sec] received
NginX + PHP-FPM Total transferred: 1590000 bytes
HTML transferred: 120000 bytes
Requests per second: 5166.39 [# / sec] (mean)
Time per request: 1.936 [ms] (mean)
Time per request: 0.194 [ms] (mean, across all concurrent requests)
Transfer rate: 801.82 [Kbytes / sec] received
Apache handles 2400 requests per second, compared to 5200 requests that for the same time processes Nginx. (basic test, almost without content)
If you work with different languages like CSS, JS and images, then NginX is more suitable for you. Its performance will be higher, but PHP will not become faster. It will also be more reliable in terms of protection from DDoS, but CDN is still the best solution.
According to statistics Netcraft nginx served or proxyed 29.38% of the most loaded sites in September 2017. Here are some examples of successful implementation of nginx: Dropbox, Netflix, Wordpress.com, FastMail.FM
Perhaps for Western countries it is not so popular yet, but here is the statistics in Russia:
I can not agree with Jeremy!
Between these projects there are significant differences that can affect the performance, opportunities and implementation time required to implement and launch each of the solutions. The choice is a series of compromises and do not neglect the tests. Ultimately, there is no one universal web server for all possible tasks, so it is important to find the solution that best suits your goals and objectives. Nginx knows 99% of everything that the modern market needs for productive work.
Basic tests show the following: Apache + mod_php
Total transferred: 3470000 bytes
HTML transferred: 120000 bytes
Requests per second: 2395.73 [# / sec] (mean)
Time per request: 4.174 [ms] (mean)
Time per request: 0.417 [ms] (mean, across all concurrent requests)
Transfer rate: 811.67 [Kbytes / sec] received
NginX + PHP-FPM Total transferred: 1590000 bytes
HTML transferred: 120000 bytes
Requests per second: 5166.39 [# / sec] (mean)
Time per request: 1.936 [ms] (mean)
Time per request: 0.194 [ms] (mean, across all concurrent requests)
Transfer rate: 801.82 [Kbytes / sec] received
Apache handles 2400 requests per second, compared to 5200 requests that for the same time processes Nginx. (basic test, almost without content)
If you work with different languages like CSS, JS and images, then NginX is more suitable for you. Its performance will be higher, but PHP will not become faster. It will also be more reliable in terms of protection from DDoS, but CDN is still the best solution.
According to statistics Netcraft nginx served or proxyed 29.38% of the most loaded sites in September 2017. Here are some examples of successful implementation of nginx: Dropbox, Netflix, Wordpress.com, FastMail.FM
Perhaps for Western countries it is not so popular yet, but here is the statistics in Russia:
https://statonline.ru/metrics/web_server_soft?tld=en
https://www.runfo.ru/statistika-rossijskogo-interneta
Given that the market share of Wordpress sites is growing daily, and Nginx works well in conjunction with Wordpress.
Using Webmin in my opinion should not impede the development of projects under Nginx. It is quite possible to use WinSCP + PuTTY.
p.s. sorry, I have bad English)