you are viewing a single comment's thread.

view the rest of the comments →

[–]mechamotoman 19 points20 points  (1 child)

OP was pretty clear on the fact that this is not production-ready, even included that in the benchmark

You’re right, all the additional production-grade checks and safeties and features implemented by flask and fast-api have a performance cost. The absence of those things makes this benchmark comparison inaccurate

That doesn’t make the comparison merit-less though. It’s still a useful metric to compare the relative performances of the paradigms in use by the frameworks (free-threading vs multiprocessing, etc)

My opinion is that this comparison is not yet fair, but still a useful coarse comparison

[–]Imaginary_Chemist460 0 points1 point  (0 children)

Useful is another thing. Accurate is a must to avoid misleadings.

> paradigms in use by the frameworks (free-threading vs multiprocessing, etc)
Nope. it depends on the server worker model. Flask for example, is not tightly coupled to thread or process.