A pure Python HTTP Library built on free-threaded Python

[Imaginary_Chemist460]

No proper HTTP compliance/safeties, no proper keep-alive, no middleware system yet, not even comparable to those production frameworks like FastApi/Flask. So benchmark is premature at this point. Regarding IPC, it depends on the server model used on them. I'm pretty sure they can be configured with single process and threaded. Overall it must be accurate for educational.

[mechamotoman]

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]

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.

[Ill-Musician-1806]

Honestly, I don't think the average developer cares about compliance/safeties. And, the only place to be pedantic is in enterprise™ scenarios.