On Sun, 07 Feb 2016 11:27:17 GMT, Márcio Martins wrote:
I definitely recommend nginx if your site has over 2K daily visitors. After running without it for about 6 months, we were left with no other option but to install it. As our traffic increased, and we added translations, our site was crashing every hour or so due to the GC running. So I installed nginx first as a means of load-balancing, but then we transitioned everything related to the transport layer to it, since it also means less garbage generated by our app.
We deploy our sites in debug mode, so we can get nice callstacks, and nice error checking and whatnot. We let nginx deal with SSL, compression, static files, redirections, etc... Then all that's left is the actual site code handling the dynamic routes which is now considerably simplified. In addition to these, you also get HTTP2 working today by simply adding a directive in your config.
I am very happy with this setup, and recommend it.
Great advice, glad I don't have to find this out the hard way. Thank you, much appreciated.
I'm curious: did you consider the possibility of forcing a GC periodically to preempt big collections, and if so, what behavior did that lead to?