cirospaciari

ASGI is a newer spec that uses async for everything (what is not really a great ideia if you is not IO bounded), so you can process more than one request at a time with ASGI if you are IO bounded, but have more overhead (a lot more) than WSGI in non IO bounded work

in the case of socketify is CPython and PyPy running the same code, but both are really fast, in the case of fiber is without prefork and with prefork variants.

Exactly

Thanks for all your support and feedback, if you want to see any new features requests, or have any questions related to the project I will be glad to help you <3

From uWS docs basically "sends into one single syscall/SSL block", in my understanding corking is basically minimizing to much sends, so it's batching calls.

WOW that's awesome!

nodejs do this and actually Go fiber uses prefork to do this too

Python GIL is the problem for multithreading, but I think I have a solution to not need 8 DB pools, soon o will post about it. But yeah it's a waste

postgresql can work with psycopg2 but is not the same performance as psycopg2cffi , i will integrate some databases to PyPy, and also HPy project will bring any Cython library to PyPy with basically the same performance or better.

<3 thanks thats means a lot, i will focus on positive comments and constructive ideas, and keep working hard to do my best.