15 karma · joined April 18, 2021
Quite a few of my clients use it to add "always up to date" screenshots to their documentation.
django, 1101 open, 32662 closed
cherrypy, 218 open, 1505 closed
starlette, 31 open, 570 closed
pyramid, 70 open, 966 closed
falcon, 168 open, 789 closed
flask, 14 open, 2318 closed
fastapi, 1044 open, 1855 closed
Fast api has one of the worst ratio regarding open/closed issues.
A while ago I benchmarked Redis vs PostgreSQL and I was initially fooled by the difference in query time. But after a deeper investigation, I realised that, even though each individual PostgreSQL request was slower, the maximum request per second when the CPU is maxed to 100% usage was pretty similar between Redis and PostgreSQL. I was benchmarking a count query with a multi-column partial index, so this might not translate at all for reading json blobs. But I think with those kind of bechmarks, one need to be very careful and shouldn't jump to conlusions that easily.
If the authors concern really is the 10ms difference it makes for each individual request, then the benchmark makes sense. But if the concern is to make the best out his server's hardware, I think his benchmark needs more work. no conclusion can be drawn at this point.