On Wed, Feb 25, 2015 at 4:12 AM, Victor Stinner wrote:
> Hi,
>
> > I also just put up another proposal to consider:
> > https://review.openstack.org/#/c/156711/
> > """Sew over eventlet + patching with threads"""
>
> My asyncio spec is unclear about WSGI, I just wrote
>
> "The spec doesn't change
Excerpts from Victor Stinner's message of 2015-02-25 02:12:05 -0800:
> Hi,
>
> > I also just put up another proposal to consider:
> > https://review.openstack.org/#/c/156711/
> > """Sew over eventlet + patching with threads"""
>
> My asyncio spec is unclear about WSGI, I just wrote
>
> "The spec
Hi,
> I also just put up another proposal to consider:
> https://review.openstack.org/#/c/156711/
> """Sew over eventlet + patching with threads"""
My asyncio spec is unclear about WSGI, I just wrote
"The spec doesn't change OpenStack components running WSGI servers
like nova-api. The specific p
I also just put up another proposal to consider:
https://review.openstack.org/#/c/156711/
"""Sew over eventlet + patching with threads"""
It goes along the thread usage case, and seems useful to consider/think
about (and if it's thrown away, that's ok IMHO, after all thats the
point of these
I’ve spent most of the past week deeply reviewing the asyncio system,
including that I’ve constructed a comprehensive test suite designed to
discover exactly what kinds of latencies and/or throughput advantages or
disadvantages we may see each from: threaded database code, gevent-based
code using