The PyPy project just posted some HTTP benchmarks that included Curio. https://morepypy.blogspot.com.br/2017/03/async-http-benchmarks-on-pypy3.html
It’s great to see Curio included in there and hanging with the other frameworks. If anything, I think it’s a real positive sign for both Curio and the sans-I/O work with libraries such as h11.
One subtle aspect of the performance graphs is the X-axis which shows the run duration of the benchmark. All of the graphs show slow speedup at first because the PyPy tracing JIT is analyzing the code. That in mind, I think it’s interesting how fast Curio ramps up to more-or-less full speed. That’s very likely a proxy for underlying code complexity. In the case of Curio, there’s just not a lot of moving parts beyond the scheduling of coroutines. So, I’m wondering if we’re seeing that reflected in the results.
I’m looking forward to playing with this more once a more official PyPy release is made.