Slow Requests on Local Flask Server

前端 未结 9 1950
无人共我
无人共我 2020-12-02 05:38

Just starting to play around with Flask on a local server and I\'m noticing the request/response times are way slower than I feel they should be.

Just a simple serve

相关标签:
9条回答
  • 2020-12-02 05:50

    Ok I figured it out. It appears to be an issue with Werkzeug and os's that support ipv6.

    From the Werkzeug site http://werkzeug.pocoo.org/docs/serving/:

    On operating systems that support ipv6 and have it configured such as modern Linux systems, OS X 10.4 or higher as well as Windows Vista some browsers can be painfully slow if accessing your local server. The reason for this is that sometimes “localhost” is configured to be available on both ipv4 and ipv6 socktes and some browsers will try to access ipv6 first and then ivp4.

    So the fix is to disable ipv6 from the localhost by commenting out the following line from my hosts file:

    ::1             localhost 
    

    Once I do this the latency problems go away.

    I'm really digging Flask and I'm glad that it's not a problem with the framework. I knew it couldn't be.

    0 讨论(0)
  • 2020-12-02 05:52

    threaded=True works for me, but finally I figured out that the issue is due to foxyproxy on firefox. Since when the flask app is running on localhost, slow response happens if

    • foxyproxy is enabled on firefox

    slow response won't happen if

    • foxyproxy is disabled on firefox

    • access the website using other browsers

    The only solution I found is to disable foxyproxy, tried to add localhost to proxy blacklist and tweak settings but none of them worked.

    0 讨论(0)
  • 2020-12-02 05:53

    Instead of calling http://localhost:port/endpoint call http://127.0.0.1:port/endpoint. This removed the initial 500ms delay for me.

    0 讨论(0)
  • 2020-12-02 05:58

    The solution from @sajid-siddiqi is technically correct, but keep in mind that the built-in WSGI server in Werkzeug (which is packaged into Flask and what it uses for app.run()) is only single-threaded.

    Install a WSGI server to be able to handle multi-threaded behavior. I did a bunch of research on various WSGI server performances. Your needs may vary, but if all you're using is Flask, then I would recommend one of the following webservers.

    Update (2020-07-25): It looks like gevent started supporting python3 5 years ago, shortly after I commented that it didn't, so you can use gevent now.

    gevent

    You can install gevent through pip with the command pip install gevent or pip3 with the command pip3 install gevent. Instructions on how to modify your code accordingly are here: https://flask.palletsprojects.com/en/1.1.x/deploying/wsgi-standalone/#gevent

    meinheld

    gevent is better, but from all the benchmarks I've looked at that involve real-world testing, meinheld seems to be the most straightforward, simplistic WSGI server. (You could also take a look at uWSGI if you don't mind some more configuration.)

    You can also install meinheld through pip3 with the command pip3 install meinheld. From there, look at the sample provided in the meinheld source to integrate Flask: https://github.com/mopemope/meinheld/blob/master/example/flask_sample.py

    *NOTE: From my use of PyCharm, the line from meinheld import server highlights as an error, but the server will run, so you can ignore the error.

    0 讨论(0)
  • 2020-12-02 05:59

    My problem was solved by "threaded=True", but I want to give some background to distinguish my problem from others for which this may not do it.

    1. My issue only arose when running Flask with python3. Switching to python2, I no longer had this issue.
    2. My problem manifested only when accessing the api with Chrome, at which point, Chrome displayed the expected screen, but everything else hung (curl, ffx, etc) until I either reloaded or closed the Chrome tab, at which point everything else that was waiting around returned a result.

    My best guess is that Chrome was trying to keep the session open and Flask was blocking the subsequent requests. As soon as the connection from Chrome was stopped or reset, everything else was processed.

    In my case, threading fixed it. Of course, I'm now going through some of the links others have provided to make sure that it's not going to cause any other issues.

    0 讨论(0)
  • 2020-12-02 06:02

    I used Miheko's response to solve my issue.

    ::1 localhost was already commented out on my hosts file, and setting Threaded=true didn't work for me. Every REST request was taking 1 second to process instead of being instant.

    I'm using python 3.6, and I got flask to be fast and responsive to REST requests by making flask use gevent as its WSGI.

    To use gevent, install it with pip install gevent

    Afterwards, I used the https://gist.github.com/viksit/b6733fe1afdf5bb84a40#file-async_flask-py-L41 to set flask to use gevent.

    Incase the link goes down, here's the important parts of the script:

    from flask import Flask, Response
    from gevent.pywsgi import WSGIServer
    from gevent import monkey
    
    # need to patch sockets to make requests async
    # you may also need to call this before importing other packages that setup ssl
    monkey.patch_all()
    
    app = Flask(__name__) 
    
    
    # define some REST endpoints... 
    
    def main():
    
        # use gevent WSGI server instead of the Flask
        # instead of 5000, you can define whatever port you want.
        http = WSGIServer(('', 5000), app.wsgi_app) 
    
        # Serve your application
        http.serve_forever()
    
    
    if __name__ == '__main__':
        main()
    
    0 讨论(0)
提交回复
热议问题