
                    For wsgi, we pick up the best solutions provided by github life savers.
                    If google brings you here, you are so lucky! These life savers are angels, they have well solved your problems.
                    So do not waste time scrolling the original issue threads just to dig out solutions... 
                    Here you are, you are welcome. Then, go back to work!
                    

The extension in the FLASK_APP env variable is removed in the documentation I'm trying to run the flaskr and minitwit examples 

flask Import error with some examples

Final summary now that our changes have landed in Github master When I perform a multipart/form-data upload of any large binary file in Flask 

werkzeug werkzeug.formparser is really slow with large binary uploads

Try using the gevent workers instead this has solved the issue for me. Using gunicorn 19.4.5 inside a docker image which is running on Ubuntu 14.04 LTS on AWS 

gunicorn Gunicorn sync workers time out on docker + AWS

Had the same issue As far as I can guess from my own logs it looks like tensorflow is using gevent and you cannot use gevent at the same time in gunicorn 

gunicorn Gunicorn + Flask + Tensorflow in Docker container doesnt work

Cross post from pallets/werkzeug#1041 :
Here is a sample Flask application for handling huge file uploads:
https://gitlab.nsd.no/ire/python-webserver-file-submission-poc/blob/master/flask_app.py
At my machine it handles a 22 GiB file in ~60 seconds

flask large file uploads eating up memory

Do we even want Flask to do any logging setup?

No Why should it? If I want to enable logging 

flask How should logging in Flask look like?

@tuukkamustonen --timeout is not meant as a request timeout It's meant as a liveness check for workers For sync workers 