gunicorn VS waitress

Yeah, that's kind of the impression I was getting. I stumbled across a github issue for gunicorn along these lines.

Taking a glimpse at gunicorn's code it looks like they pretty much all do the same: 2. seems to be creating a wsgi app using django's internals, and 3. uses 2.

gunicorn: Python WSGI HTTP Server.

2015-03-11 09:42:06 [25641] [DEBUG] GET /Will this print? Looking around, I've tried to redirect all output to gunicorn logs, then starting gunicorn like this:

I did some googling and just realized I'm using ALB not ELB, not sure yet if that makes a huge difference for this particular issue. I found the github issue which unfortunately was closed: https://github.com/benoitc/gunicorn/issues/1194

I found that some discussion in the gc.freeze() PR. It looks that the untouched data should be able to share among processes. Also, it has been 4 years for Gunicorn to process this support for gc.freeze() for apps that use preloading. I cannot found a good example to demonstrate that this method works well.

gunicorn: This will install the gunicorn

I have spent hours reviewing and testing ways of making waitress exit cleanly (like this and this) but the best I can do so far is a kind of suicidal SIGINT which makes Windows complain "the pipe has been ended" when stopping through the Services control panel, but at least it stops :-/ I guess the pythonservice.exe which pywin32 starts, should not terminate, just the waitress treads?

Waitress - for serving your application easily (pairs very well with Whitenoise).

If you’re delegating your load balancing to something else further up the stack and would prefer a simpler WSGI server than Gunicorn, Waitress is worth a look: https://github.com/pylons/waitress