On Thursday, September 12, 2019 at 1:54:53 PM UTC-4, Theron Luhn wrote: > > Usually you put an HTTP server like nginx or HAProxy in front of your WSGI > server, which are very good at handling high-volume HTTP requests, so that > your WSGI server isn't subjected to whatever the internet might send your > way. >
in addition to that: * I've found a forking server like uwsgi / gunicorn to be the most performant strategy for most situations, as their "max_requests" settings to restart workers will eliminate most issues with process growth or memory leaks. they both also offer numerous deployment and management benefits and in addition to what Bert said... every deployment strategy has a pros and cons that are from tradeoffs in the design of the infrastructure. there is no overall "best option". your code could run blazingly fast on one stack with specific resources, and run terribly on another. while i have a handful of apps that could redeploy using a single-process strategy with no impact, moving my main app from a forked multi-process model to a series of single-process containers would greatly increase our cloud computing bills (we tested it a while back, and it would have required way more servers/resources). -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/4459efb5-7ba5-487d-8409-3089ad3c308b%40googlegroups.com.
