2 ms·
Just a quick look over the code of the Django and Flask benchmarks reveals, that they are both run in debug mode introducing significant overhead. In addition
by DasIch 12y ago
Just a quick look over the code of the Django and Flask benchmarks reveals, that they are both run in debug mode introducing significant overhead.
In addition that that database access isn't performed asynchronously, which leaves the question about what is actually supposed to happen asynchronously.
- mrj 12y agoThe json serialization is also very different. Flask is using json.dumps while the django code is using a custom JsonResponse class that includes an isinstance check.