0

I have developed a HTTP API endpoint using flask which accepts json data on POST requests and sends back json response.

I have tried using multiple WSGI servers: gunicorn, cheroot, Bjoern behind Nginx as a reverse proxy.

I noticed that no matter which WSGI server I use, the application is unable to handle a sustained loads of 500 requests per second. A sudden burst of 500 is handled fine. But not when it is sustained. The requests start getting delayed responses and quite a few requests just time out.

The flask web is deployed on a 24 core physical server. So it has 48 logical cores. I am using a C++ application on another similar 24 core server to fire these requests asynchronously. One request every 2ms, thus 500 per second.

Consider the below example of the simple single file flask application on cheroot WSGI server I created to benchmark the performance. It only logs the request json and sends back a response json. Even this is unable to handle a sustained load of 500 requests on a powerful 24 core physical server. The CPU usage is always below 5% during the test.

import os
import json
import logging
from logging.handlers import TimedRotatingFileHandler
from flask import Flask
from flask import request, jsonify
from cheroot.wsgi import PathInfoDispatcher
from cheroot.wsgi import Server

app = Flask(__name__)

# Setup logger for the app
if not os.path.exists('logs'):
        os.mkdir('logs')
file_handler = TimedRotatingFileHandler('logs/simpleflaskapp.log', when='midnight', interval=1, backupCount=10)
file_handler.setFormatter(logging.Formatter(
    '%(asctime)s %(levelname)s: %(message)s [in %(pathname)s:%(lineno)d]'))
file_handler.setLevel(logging.INFO)
app.logger.addHandler(file_handler)

app.logger.setLevel(logging.INFO)
app.logger.info("simpleflaskapp startup")
# end setup logger

@app.route( '/test', methods = [ 'POST' ] )
def test():
    app.logger.info(json.dumps(request.json))
    res = {
        "statusCode": 200,
        "message": "OK",
    }
    return jsonify(res)

d = PathInfoDispatcher({'/': app})
server = Server(('0.0.0.0', 8000), d, numthreads=os.cpu_count(), request_queue_size=int(os.cpu_count()/2))

if __name__ == '__main__':
    try:
        server.start()
    except KeyboardInterrupt:
        server.stop()

The author of the blog post https://www.appdynamics.com/blog/engineering/a-performance-analysis-of-python-wsgi-servers-part-2/ is able to serve multiple thousands of requests per second on a 2 core machine. What am I doing wrong?

Eliminating the disk IO by commenting out logging in the above sample app, allows me to reach 666 requests per second. But not more. This is still low considering the hardware I am running it on.

I have already checked the Nginx configuration and it is configured to handle much higher loads. I have also tried firing requests directly to the WSGI server skipping Nginx and the results of that are worse.

1
  • Could you please care to explain the reason for the downvote?
    – Nithish
    May 18, 2021 at 17:05

1 Answer 1

1

Answering my own question.

After going nowhere with trying various WSGI servers with flask, I decided to give cherrypy a try. Turns out even that has similar limitation on concurrency.

Then I came across Sanic. I wrote the same test application on sanic and I am able consistently handle even 10000 requests per second.

Migrating my project from flask to sanic now.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .