|
|
|
|
|
| Re: Integrated nginx in kloxo [message #105749 is a reply to message #105725] |
Thu, 28 February 2013 16:07   |
|
garettwarne wrote on Mon, 25 February 2013 17:21Yes I agree with the id developer.
As I know, LxCenter no planning for next release (6.2.x). Just stuck on 6.1.x.
It's why I make my own Kloxo fork.
|
|
|
| Re: Integrated nginx in kloxo [message #106080 is a reply to message #105749] |
Thu, 04 April 2013 07:29  |
ArcAiN6  Messages: 113 Registered: July 2008 |
Valuable Member |
|
|
nginx probably should be available as an option, but i don't wish for it to be the default option.
nginx isn't very suited for shared hosting.
You might think that if you let nginx handle just static files while proxying non-existing files and dynamic files to Apache then you'll be good. This isn't quite the case, though. As an example, consider basic authentication, if you want to have basic authentication on a static file then you will need to add it in the nginx configuration, and users cannot do this without having to reload the configuration file. If you allow them to change it and reload it then they can make a mistake and ruin it for everyone.
While nginx is faster at serving static files and consumes much less memory for concurrent requests this is due to nginx not needing to wait onf scripts to process, however, this speed increase is negated the second you decide to implement php, php-fastcgi, or php-fpm, or a mysql layer as it will then become just as fast / slow as apache waiting for the php script or mysql to process.
This also doesn't take into consideration the myriad of other features that would need to be exported to a running apache process for functionality, such as cgi, or more importently WebDAV.
All that being said. if all you do is serve static pages, then nginx is the way to go, but if you serve pages with php, webdav access, or mysql layers, you are wasting your time, as any speed gained by nginx is lost within the php/mysql layers, as well as you would also have apache running, so the memory gains from nginx actually turn into a loss as now both nginx, and apache are running.
|
|
|